Em Seg, 2009-03-09 às 21:38 -0300, Euler Taveira de Oliveira escreveu:
> Magnus Hagander escreveu:
> > I'm not sure it's worth going over the whole code with pgindent or
> > similar though - it makes it so much harder to backtrack the code in
> > svn. Especially since we haven't had a standard before, it'll likely
> > touch way too much code.
> >
> What about do it after next release? Looking at the source code, almost
> everything uses 4 spaces per level so we could go through this way.
I don't know if somebody did it yet bu just for information.
$ cd ~/src/pgadmin3/pgadmin
$ LC_ALL=en_US svn update
At revision 7657.
$ find ./ -name "*.cpp" -exec egrep "^([[:space:]]{4}|\t)+" {} \; | wc
-l
47911 matching lines started with 4 spaces or tabs
$ find ./ -name "*.cpp" -exec egrep -H "^([[:space:]]{4}|\t)+" {} \; |
cut -d':' -f1 | sort | uniq | wc -l
273 files matching lines started with 4 space or tabs
[]s
Dickson S. Guedes
mail/xmpp: gue...@guedesoft.net - skype: guediz
http://guedesoft.net - http://planeta.postgresql.org.br
--
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers
