search

MapServer / MapServer-import

3 stars 2 forks source link

Clean up mapservObj member names... #472

Open tbonfort opened 12 years ago

tbonfort commented 12 years ago

Reporter: sdlime Date: 2003/10/28 - 00:59

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.
tbonfort commented 12 years ago

Author: dmorissette Date: 2004/04/17 - 07:24

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.
tbonfort commented 12 years ago

Author: sgillies@frii.com Date: 2004/05/30 - 00:50

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.
tbonfort commented 12 years ago

Author: sdlime Date: 2007/08/08 - 07:50 Since this is really just housekeeping it tends to slip. Here it goes again... to 5.2.

Steve

tbonfort commented 12 years ago

Author: sdlime Date: 2008/04/12 - 17:40 I'm actually doing this as part of RFC 36 implementation.

Steve

tbonfort commented 12 years ago

Author: sdlime Date: 2008/06/21 - 15:01 I'll finish this in 5.4...

Steve