[postgis-devel] astyle

Kevin Neufeld kneufeld at refractions.net
Fri May 22 14:30:48 PDT 2009


In keeping with this policy, I propose the same be done to the xml files we are using for documentation.  In this way, 
content changes can be easily separated from style changes.

I found xmlformat - a free, configurable, xml pretty printer that seems to do the same thing astyle does for c.  We can 
customize the formatter so that some tags can be treated as blocks with indented tags, others as inline, and others as 
verbatim (like <programlisting>).

If anyone has any better ideas, I'm all ears, but I wouldn't mind seeing the code base adopt some style convention.

Cheers,
Kevin

Paul Ramsey wrote:
> If you've edited PostGIS source, you've quickly become frustrated with
> the ghastly mix of tabs and spaces used to format code. I would like
> to propose that we begin re-formatting the source incrementally, by
> making the use of
> 
> astyle --style=ansi --indent=tab=8
> 
> on any .c/.h files we are about to modify.
> 
> - I'm about to modify foo.c!
> - astyle --style=ansi --indent=tab=8 foo.c
> - svn commit -m "Reformat!" foo.c
> - remember to set my editor to use tabs, not spaces, for block indents
> - Ok, make my changes now.
> 
> Sound OK?
> 
> Paul
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel



More information about the postgis-devel mailing list