On Monday, 07 January 2008, at 21:06:04 (+0100), Kim Woelders wrote: > (and the line length is set to 80 of course :) ).
I got into the habit of using 132 instead of 80 because 80 columns is all too often not enough for readability, particularly when using lengthier OO-style function naming (namespace_object_action(OBJECT_CAST(object), ...) -- See how ugly that wrapped? Ick!), and the vast majority of terminals (including xterm and Eterm) have 80/132 column toggles built-in, even key-bindable. To me, sticking with an 80-column limit for coding is like using gcc 2.7.2.3 to compile all your software: it was great 10 years ago, but we live in a different world now. Even the Linux console itself can do well beyond 80 columns. :) But tabs vs. spaces is far more likely to result in spaghetti code then setting the column limit. Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ <[EMAIL PROTECTED]> Linux Server/Cluster Admin, LBL.gov Author, Eterm (www.eterm.org) ----------------------------------------------------------------------- "A leader takes people where they want to go. A great leader takes people where they don't necessarily want to go, but ought to be." -- Rosalynn Carter ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
