Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.programming > #2692

Re: programmer's keyboard

From BGB <cr88192@hotmail.com>
Newsgroups comp.programming
Subject Re: programmer's keyboard
Date 2012-12-30 02:12 -0600
Organization albasani.net
Message-ID <kbot6e$t1j$1@news.albasani.net> (permalink)
References (5 earlier) <_sWdnYhcjvIJl0LNnZ2dnUVZ8sadnZ2d@bt.com> <kbnkla$k1b$1@news.albasani.net> <R%IDs.81296$1y.64372@fx01.am4> <kbnnb5$q3r$1@news.albasani.net> <QkKDs.979409$vW7.448572@fx19.am4>

Show all headers | View raw


On 12/29/2012 4:41 PM, BartC wrote:
> "BGB" <cr88192@hotmail.com> wrote in message
> news:kbnnb5$q3r$1@news.albasani.net...
>> On 12/29/2012 3:10 PM, BartC wrote:
>
>>> (Also, they clash with the use of the same #if/#endif symbols for
>>> commenting out code, which is a different requirement; you might not
>>> want that code deleted when you come across it much later.)
>>>
>>
>> usually, for comments, either // or /* ... */ is used.
>>
>> /*
>>  * somePseudoCode();
>>  * morePseudoCode();
>>  *
>>  */
>
> Won't work in general because C /*...*/ comments don't nest. In fact
> when I argued the case for having nestable /*...*/ comments in
> comp.lang.c, I was advised to use #if for the purposes of commenting out
> code!
>

/* ...*/ nesting doesn't actually usually matter...


ironically, for actually commenting out lines of code, I generally use 
'//' comments.

usually, /* ... */ is for stuff that is *always* comments.

so:
//	CommentedLineOfCode();

/* Something said about code. */

/* ... */

would then only really be used in the case where any code is itself 
comment, as in the example, as non-functional pseudo-code (usually there 
only really to summarize the high-level intent).

block enabling/disabling code then comes back to #if or "if() {...}", 
where the choice as to which is used depends a fair amount on what the 
code is doing.


sometimes, it has ended up as:
if(FOO_DebugP(ctx))
{
	...
}

or similar, such as enabling debug prints or similar only if debugging 
is enabled for a given context.


>>> The thing about writing in capitals, or using special indentation, is
>>> that
>>> each line stands out by itself without relying on editing features.
>>>
>>
>> but, OTOH, you can end up with unintended identifier clashes between
>> symbols differing only in case.
>>
>> it also fouls up naming conventions which rely on, say, "foo" and
>> "Foo" being disjoint ("foo" for private members, "Foo" for public
>> members), and the standard use of "FOO" for constant values.
>
> If the language is case-sensitive then you can't just switch to capitals
> anyway.
>
> If the language doesn't care about case (such as all of mine), then
> those problems don't come up. (Except when interfacing to foreign
> functions where correct case is important, and then the name is only
> needs declaring properly once. The incidence of two foreign function
> names clashing when case is disregarded, is rare.)
>

most of my languages are case-sensitive.

to me, case sensitivity just "makes sense".

Back to comp.programming | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

programmer's keyboard bob <bob@coolfone.comze.com> - 2012-12-26 11:45 -0800
  Re: programmer's keyboard Robert Wessel <robertwessel2@yahoo.com> - 2012-12-26 15:01 -0600
    Re: programmer's keyboard "BartC" <bc@freeuk.com> - 2012-12-26 21:36 +0000
      Re: programmer's keyboard BGB <cr88192@hotmail.com> - 2012-12-26 21:12 -0600
      Re: programmer's keyboard Robert Wessel <robertwessel2@yahoo.com> - 2012-12-27 23:45 -0600
        Re: programmer's keyboard "BartC" <bc@freeuk.com> - 2012-12-28 13:46 +0000
          Re: programmer's keyboard Ian Collins <ian-news@hotmail.com> - 2012-12-29 11:42 +1300
          Re: programmer's keyboard "Chris Uppal" <chris.uppal@metagnostic.REMOVE-THIS.org> - 2012-12-29 15:15 +0000
            Re: programmer's keyboard BGB <cr88192@hotmail.com> - 2012-12-29 14:41 -0600
              Re: programmer's keyboard "BartC" <bc@freeuk.com> - 2012-12-29 21:10 +0000
                Re: programmer's keyboard BGB <cr88192@hotmail.com> - 2012-12-29 15:26 -0600
                Re: programmer's keyboard "BartC" <bc@freeuk.com> - 2012-12-29 22:41 +0000
                Re: programmer's keyboard BGB <cr88192@hotmail.com> - 2012-12-30 02:12 -0600
                Re: programmer's keyboard "BartC" <bc@freeuk.com> - 2012-12-30 11:20 +0000
                Re: programmer's keyboard malcolm.mclean5@btinternet.com - 2012-12-30 10:19 -0800
                Re: programmer's keyboard BGB <cr88192@hotmail.com> - 2012-12-30 14:51 -0600
              Re: programmer's keyboard Ian Collins <ian-news@hotmail.com> - 2012-12-30 10:43 +1300
                Re: programmer's keyboard BGB <cr88192@hotmail.com> - 2012-12-30 01:55 -0600
                Re: programmer's keyboard Ian Collins <ian-news@hotmail.com> - 2012-12-30 21:06 +1300
                Re: programmer's keyboard BGB <cr88192@hotmail.com> - 2012-12-30 02:35 -0600
                Re: programmer's keyboard Rui Maciel <rui.maciel@gmail.com> - 2012-12-30 18:12 +0000
                Re: programmer's keyboard BGB <cr88192@hotmail.com> - 2012-12-30 13:30 -0600
                Re: programmer's keyboard Ian Collins <ian-news@hotmail.com> - 2012-12-31 09:36 +1300
                Re: programmer's keyboard BGB <cr88192@hotmail.com> - 2012-12-30 17:27 -0600
                Re: programmer's keyboard Ian Collins <ian-news@hotmail.com> - 2012-12-31 13:00 +1300
                Re: programmer's keyboard BGB <cr88192@hotmail.com> - 2012-12-31 03:13 -0600
                version control (was: Re: programmer's keyboard) rugxulo@gmail.com - 2012-12-31 10:36 -0800
                Re: programmer's keyboard Ian Collins <ian-news@hotmail.com> - 2013-01-01 09:05 +1300
                Re: programmer's keyboard BGB <cr88192@hotmail.com> - 2012-12-31 16:58 -0600
                Re: programmer's keyboard Ian Collins <ian-news@hotmail.com> - 2013-01-01 13:24 +1300
                Re: programmer's keyboard Rui Maciel <rui.maciel@gmail.com> - 2013-01-02 12:23 +0000
                Re: programmer's keyboard BGB <cr88192@hotmail.com> - 2013-01-02 14:34 -0600
                Re: programmer's keyboard Robert Wessel <robertwessel2@yahoo.com> - 2013-01-02 15:35 -0600
                Re: programmer's keyboard BGB <cr88192@hotmail.com> - 2013-01-03 13:19 -0600
                Re: programmer's keyboard Willem <willem@turtle.stack.nl> - 2013-01-03 08:35 +0000
                Re: programmer's keyboard BGB <cr88192@hotmail.com> - 2013-01-03 13:46 -0600
                Re: programmer's keyboard rugxulo@gmail.com - 2013-01-03 00:52 -0800
                Re: programmer's keyboard Rui Maciel <rui.maciel@gmail.com> - 2013-01-03 15:00 +0000
                Re: programmer's keyboard Rui Maciel <rui.maciel@gmail.com> - 2013-01-02 11:58 +0000
                Re: programmer's keyboard BGB <cr88192@hotmail.com> - 2013-01-02 15:03 -0600
                Re: programmer's keyboard rugxulo@gmail.com - 2013-01-03 00:54 -0800
                Re: programmer's keyboard BGB <cr88192@hotmail.com> - 2013-01-03 13:06 -0600
                Re: programmer's keyboard Rui Maciel <rui.maciel@gmail.com> - 2012-12-30 18:04 +0000
                Re: programmer's keyboard BGB <cr88192@hotmail.com> - 2012-12-30 14:24 -0600
                Re: programmer's keyboard Rui Maciel <rui.maciel@gmail.com> - 2013-01-02 11:34 +0000
          Writing Experimental Code "Aaron W. Hsu" <arcfide@sacrideo.us> - 2013-01-02 15:08 -0600
  Re: programmer's keyboard Rui Maciel <rui.maciel@gmail.com> - 2012-12-28 11:45 +0000
    Re: programmer's keyboard BGB <cr88192@hotmail.com> - 2012-12-28 12:29 -0600

csiph-web