Clean up mapservObj member names...

[sdlime]

They are named unlike anything else in the code. There are a few vars in there
that have very cryptic names (e.g. LRN). This would involve some changes to
mapserv.c, mapserv_fcgi.c and maptemplate.c. I don't know how prevelant this
object is in the scripting envs.

[dmorissette]

mapservObj comes from our end, and the source of the problem is a collision
between our coding style and yours. Let's work on this together during the 4.3
release cycle to cleanup the mapservObj. 

Perhaps at the same time we could come up with a documented coding style that
mapserver developers should follow... it doesn't have to be long, just a few
guidelines on naming variables, files, indenting of code, etc.

[sgillies@…]

How about we use the wiki to document the minimum number of rules?
We could start here:

http://mapserver.gis.umn.edu/cgi-bin/wiki.pl?MapServerCodingStandards

I began with some style notes that impact the MapScript API, my 
particular area of interest.  I can adapt to whatever is decided for
C style in general.  I'm agnostic about braces, and like 4-space 
indentation.  No tabs.

[dmorissette]

DMSG Coding Style

[sdlime]

Since this is really just housekeeping it tends to slip. Here it goes again... to 5.2.

Steve

[sdlime]

I'm actually doing this as part of RFC 36 implementation.

Steve

[sdlime]

I'll finish this in 5.4...

Steve