> As Stefan Tauner wrote: > >> skimmed over (the getopt code in) main() and was greeted by a creative >> variation of whitespace behavior (8-unit tabs + 4-unit spaces) :( > Well, there's nothing wrong with that per se. Alas, there are other > functions apparently written with the assumption that one hard tab > occupies four columns, and in even other cases, there are four spaces > in front of the first tab. :/ Plus, a lot of trailing whitespace all > over the file. Welcome to communal software development! When many different people contribute, you're bound to get a mix. Stefan's original code used a "unique" indentation method (2 spaces to start, then +4 spaces for each level afterward)...I'm assuming he was using some specific Emacs modeline for his coding.
Me, I use a simple text editor (no modeline support) and prefer 1 tab char per indentation level. Among other things, this lets the user set his viewer to indent however much he/she wants for visual clarity. With my current setup, it's almost impossible for me to recreate special modelines, so I would definitely prefer to switch everything over to tabs. Cheers-- Julian ------------------------------------------------------------------------------ What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d _______________________________________________ Gerbv-devel mailing list Gerbv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gerbv-devel
