On Mon, Apr 13, 2009 at 4:09 PM, David Kelly dke...@hiwaay.net wrote:
On Mon, Apr 13, 2009 at 10:46:26AM +0200, deeptec...@gmail.com wrote:
Tabs are better, because they allow the programmer to specify the
desired width, and is dynamically changable at any time.
Spaces are better because
Matthew D. Fuller wrote:
On Wed, Apr 15, 2009 at 10:20:08AM +0300 I heard the voice of
Giorgos Keramidas, and lo! it spake thus:
switch (value) {
case SOME_CONSTANT_NAME:do_stuff_here();break;
case ANOTHER_CONSTANT_NAME:
retarded mixes of
tabs and spaces. But generally it's hard to implement an editor which
controls retarded of any ASCII character. So let's only consider
well-formed files. For such files, my whitespace style applies: if
indentation is width-critical, use spaces, otherwise (like C source) use
tabs
only consider
well-formed files. For such files, my whitespace style applies: if
indentation is width-critical, use spaces, otherwise (like C source) use
tabs precisely for indentation. What do you want from not well-formed files?
A space is a well-defined thing. It behaves like any other
On Wed, 15 Apr 2009 06:48:12 +0200, deeptec...@gmail.com wrote:
Could you please give me a (preferrably widely used) example of
columnizing calls which cross different levels of indentation?
It's not so uncommon as it may initially seem...
I've seen switch() cases in several programs indented
On Wed, Apr 15, 2009 at 10:20:08AM +0300 I heard the voice of
Giorgos Keramidas, and lo! it spake thus:
switch (value) {
case SOME_CONSTANT_NAME:do_stuff_here();break;
case ANOTHER_CONSTANT_NAME: do_some_other_stuff(); break;
David Kelly wrote:
On Apr 14, 2009, at 6:24 PM, deeptec...@gmail.com wrote:
David Kelly wrote:
On Mon, Apr 13, 2009 at 10:46:26AM +0200, deeptec...@gmail.com wrote:
Tabs are better, because they allow the programmer to specify the
desired width, and is dynamically changable at any time.
