Re: Where do I start?

From: Jan Panteltje (pNaonStpealmtje_at_yahoo.com)
Date: 02/14/05


Date: Mon, 14 Feb 2005 22:04:09 GMT

On a sunny day (14 Feb 2005 19:40:14 GMT) it happened Grant Edwards
<grante@visi.com> wrote in <4210fe9e$0$41681$a1866201@visi.com>:

>On 2005-02-14, Jan Panteltje <pNaonStpealmtje@yahoo.com> wrote:
>
>>>> That would make my C code a pain to maintain.
>>>
>>>Python is the language under discussion, not C. Using an
>>
>> Always thought python was a sort of snake....
>
>Many words have more than one meaning. One chooses from
>amongst the meanings based on context.
That can be really dangerous ..... would have to think about an
example though.

>>>editor's Python mode to edit C code wouldn't be a rather bad
>>>idea.
>
>> Is not a text editor enough to edit ANY source code?
>
>No, not in my opinion. I expect the editor I use to edit
>source to be aware of the syntax and semantics of the language
>in use.
That is a point, I have though about it some times.
I have for example used MS visual studio and it colors C functions
uses separate color for comments, you know the stuff better then me I am sure.

I have come the the following conclusion for myself:
I do not like this:

for(i=0;i<100;i++){do_something(flip);}

If somebody types: 'Idolikeallwordsinasentencetobegluedtogether' that is just
as bad in my view.
I like it like this:
for( i = 0; i < 100; i++) ...
When one writes code like this, then there is not a whole lot of need for
coloring 'for', also properly using spaces (as you would pronounce it in
normal language) really helps *me* with overview.
a<=b|c; //sucksalot
a <= b | c; // sucks less IMO.

Also I do not see many books in English that color each word (except for
3 years old to learn writing), somehow we are able to recognize these if
properly separated by spaces.

Small difference is in libc.info all functions are described as foo ()
while I myself write foo().
Perhaps because I think the parenthesis are part of the function name...

I am sure there are as many preferences as people in all this.
Just like editors, and languages...
I speak C, a little C++, 10 sorts of assembler, a little bash, and I can read
perl, but would have big problems writing it.
I also speak English, Dutch, French, German, Portuguese a little, and 2 words
Chinese, fragments of some other languages.
It may or may not have influence on the fact I want those spaces....
But I DO want to make a case here for not 'gluing' everything together in
computer languages.
And proper indentation in C! Keep things aligned! Best way to find a problem.
OK I will now step of my soap box (or soapbox?) hehe ;-) to let others do it
their way...



Relevant Pages

  • Re: OOP php user system
    ... never actually programmed proper OO code yet. ... languages' get/set construct. ... rather to always have getter and setter methods. ... Jerry, Jerry, Jerry! ...
    (comp.lang.php)
  • Re: OOP php user system
    ... never actually programmed proper OO code yet. ... to rig the jury to obtain the get/set functionality that is supplied ... rather to always have getter and setter methods. ... That's why you won't find them in good OO languages such as SmallTalk, ...
    (comp.lang.php)
  • Re: OOP php user system
    ... never actually programmed proper OO code yet. ... rather to always have getter and setter methods. ... That's why you won't find them in good OO languages such as ... Jerry, Jerry, Jerry! ...
    (comp.lang.php)
  • Re: OOP php user system
    ... never actually programmed proper OO code yet. ... rather to always have getter and setter methods. ... That's why you won't find them in good OO languages such as SmallTalk, ... Jerry, Jerry, Jerry! ...
    (comp.lang.php)
  • Re: OOP php user system
    ... never actually programmed proper OO code yet. ... to rig the jury to obtain the get/set functionality that is supplied by ... rather to always have getter and setter methods. ... That's why you won't find them in good OO languages such as SmallTalk, ...
    (comp.lang.php)