[fdo-dev] Naming convention for RDBMS UnitTest

Greg Boone greg.boone at autodesk.com
Mon Aug 28 11:41:20 EDT 2006

Hi Mateusz,

There is no absolute guideline for naming local function variables. You
will find all 3 used and code reviews have not been looking explicitly
for this issue. You are correct that option 3 is not heavily used. I and
many others have been using option 2. Since this is not a big issue, I
would recommend sticking with what you already have implemented and
moving forward.


-----Original Message-----
From: Mateusz Loskot [mailto:mateusz at loskot.net] 
Sent: Monday, August 28, 2006 10:53 AM
To: dev at fdo.osgeo.org
Subject: Re: [fdo-dev] Naming convention for RDBMS UnitTest

Dan Stoica wrote:
> Mateusz, go with 3. T* pMyObject.

I didn't expected that choice ;-)
I mean, I've learned the FDO style from reading the code
and I rarely see use of 'p' prefix for pointers.
I'd say, FDO uses .NET-like coding guidelines from MSDN.

Or does this 'p' prefix rule apply only to Unit Tests?

If it applies to all FDO code, I'll grep & sed my PostGIS files and
change it to pMyObject naming style.

Mateusz Loskot

To unsubscribe, e-mail: dev-unsubscribe at fdo.osgeo.org
For additional commands, e-mail: dev-help at fdo.osgeo.org

More information about the Fdo-internals mailing list