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

Groups > comp.lang.c++ > #48160 > unrolled thread

Whitespace and (borked) comments.

Back to article view | Back to comp.lang.c++

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Whitespace and (borked) comments. Jeff-Relf.Me <@.> - 2017-01-19 02:24 -0800
    Re: Whitespace and (borked) comments. Peter Köhlmann <peter-koehlmann@t-online.de> - 2017-01-19 11:30 +0100
      Re: Whitespace and (borked) comments. chrisv <chrisv@nospam.invalid> - 2017-01-19 07:29 -0600
        Re: Whitespace and (borked) comments. woodbrian77@gmail.com - 2017-01-19 09:58 -0800
          Re: Whitespace and (borked) comments. red floyd <dont.bother@its.invalid> - 2017-01-19 13:25 -0800
      Re: Whitespace and (borked) comments. Jerry Stuckle <jstucklex@attglobal.net> - 2017-01-19 10:36 -0500
        Re: Whitespace and (borked) comments. Peter Köhlmann <peter-koehlmann@t-online.de> - 2017-01-19 16:48 +0100
    Re: Whitespace and (borked) comments. GreyCloud <mist@cumulus.com> - 2017-01-19 11:20 -0700
    Re: Whitespace and (borked) comments. moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-20 04:26 +0000
      About a hundred thousand people have used my code, last 24 years. Jeff-Relf.Me <@.> - 2017-01-19 20:57 -0800
        Re: About a hundred thousand people have used my code, last 24 years. Öö Tiib <ootiib@hot.ee> - 2017-01-20 00:17 -0800
          Re: How do you pronounce "Oo" ? Öö Tiib <ootiib@hot.ee> - 2017-01-20 00:57 -0800
            Re: How pronounced is the 'r" ? is it long, like errr ? Öö Tiib <ootiib@hot.ee> - 2017-01-20 03:50 -0800
      Re: Whitespace and (borked) comments. jmfbahciv <See.above@aol.com> - 2017-01-20 13:39 +0000
        Re: Whitespace and (borked) comments. chrisv <chrisv@nospam.invalid> - 2017-01-20 07:46 -0600
          Re: Whitespace and (borked) comments. jmfbahciv <See.above@aol.com> - 2017-01-21 14:08 +0000
        Re: Whitespace and (borked) comments. Vir Campestris <vir.campestris@invalid.invalid> - 2017-01-20 22:02 +0000
          Re: Whitespace and (borked) comments. jmfbahciv <See.above@aol.com> - 2017-01-21 14:08 +0000
            Re: Whitespace and (borked) comments. Vir Campestris <vir.campestris@invalid.invalid> - 2017-01-22 17:58 +0000

#48160 — Whitespace and (borked) comments.

Michael Moroney wrote:
> professional coders write with future maintainability in mind.

One doesn't buy a Ferrai becuse it's "maintainable".

Running the code, testing it,
is how one knows what's up, not whitespace and (borked) comments.

If whitespace and (borked) comments is what you need/like,
then add them yourself, later... _I don't want to see that crap.

[toc] | [next] | [standalone]

#48161

 wrote:

> Michael Moroney wrote:
>> professional coders write with future maintainability in mind.
> 
> One doesn't buy a Ferrai becuse it's "maintainable".
> 
> Running the code, testing it,
> is how one knows what's up, not whitespace and (borked) comments.
> 
> If whitespace and (borked) comments is what you need/like,
> then add them yourself, later... _I don't want to see that crap.

Idiot

[toc] | [prev] | [next] | [standalone]

#48174

Peter Köhlmann wrote:

> Relf wrote:
>>
>> Michael Moroney wrote:
>>>
>>> professional coders write with future maintainability in mind.
>> 
>> One doesn't buy a Ferrai becuse it's "maintainable".

Trolling 101.  Claim the exact opposite of the truth.  As if Relf's
garbage is a high-performance, well-engineered machine.
 
>> Running the code, testing it,
>> is how one knows what's up, not whitespace and (borked) comments.
>> 
>> If whitespace and (borked) comments is what you need/like,
>> then add them yourself, later... _I don't want to see that crap.
>
> Idiot

Think on the fact that the Relf kook has been spewing this same
bullshit, defending his idiotic practices against *countless* attempts
to explain the errors of his way, for almost two decades!

Look below at what DumFSck wrote, after I called Relf's statements,
eschewing the importance of compiler-time warnings, "stupid".  I mean,
what kind of *fscking* idiot would write such ridiculous garbage?

-- 
"ALL non-idiots support the use of testing over compile-time warnings
to determine if the code functions correctly.  You're one of the few
idiots who thinks otherwise."  -  "DFS"

[toc] | [prev] | [next] | [standalone]

#48189

On Thursday, January 19, 2017 at 7:29:58 AM UTC-6, chrisv wrote:


Please don't swear here.


Brian
Ebenezer Enterprises - In G-d we trust.
http://webEbenezer.net

[toc] | [prev] | [next] | [standalone]

#48200

On 1/19/2017 9:58 AM, woodbrian77@gmail.com wrote:
> On Thursday, January 19, 2017 at 7:29:58 AM UTC-6, chrisv wrote:
>
>
> Please don't swear here.
>

Fuck off about this already.

[toc] | [prev] | [next] | [standalone]

#48187

On 1/19/2017 5:30 AM, Peter Köhlmann wrote:
>  wrote:
> 
>> Michael Moroney wrote:
>>> professional coders write with future maintainability in mind.
>>
>> One doesn't buy a Ferrai becuse it's "maintainable".
>>
>> Running the code, testing it,
>> is how one knows what's up, not whitespace and (borked) comments.
>>
>> If whitespace and (borked) comments is what you need/like,
>> then add them yourself, later... _I don't want to see that crap.
> 
> Idiot
> 

What do you have against idiots that you insult them like this?

-- 
==================
Remove the "x" from my email address
Jerry Stuckle
jstucklex@attglobal.net
==================

[toc] | [prev] | [next] | [standalone]

#48188

Jerry Stuckle wrote:

> On 1/19/2017 5:30 AM, Peter Köhlmann wrote:
>>  wrote:
>> 
>>> Michael Moroney wrote:
>>>> professional coders write with future maintainability in mind.
>>>
>>> One doesn't buy a Ferrai becuse it's "maintainable".
>>>
>>> Running the code, testing it,
>>> is how one knows what's up, not whitespace and (borked) comments.
>>>
>>> If whitespace and (borked) comments is what you need/like,
>>> then add them yourself, later... _I don't want to see that crap.
>> 
>> Idiot
>> 
> 
> What do you have against idiots that you insult them like this?
> 

I know that the real idiots don't deserve to be compared with a lunatic twit 
like that Relf imbecile. But for the lack of better words to describe that 
dimbulb...

[toc] | [prev] | [next] | [standalone]

#48190

Jeff-Relf.Me <@.> wrote:

> Michael Moroney wrote:
>> professional coders write with future maintainability in mind.
> 
> One doesn't buy a Ferrai becuse it's "maintainable".
> 
> Running the code, testing it,
> is how one knows what's up, not whitespace and (borked) comments.
> 
> If whitespace and (borked) comments is what you need/like,
> then add them yourself, later... _I don't want to see that crap.

But your follow-up coders will.  It helps them to understand how the code was 
written and for what.

[toc] | [prev] | [next] | [standalone]

#48208

Jeff-Relf.Me <@.> writes:

>Michael Moroney wrote:
>> professional coders write with future maintainability in mind.

>One doesn't buy a Ferrai becuse it's "maintainable".

Irrelevant comparison. Whitespace and comments don't slow code down in
compiled languages.

>If whitespace and (borked) comments is what you need/like,
>then add them yourself, later... _I don't want to see that crap.

Maybe you don't, but certainly the next guy who comes along to fix/improve/
modernize it will.  Otherwise it may have the shelf life of a banana,
once you have moved on/retired/died.

[toc] | [prev] | [next] | [standalone]

#48212 — About a hundred thousand people have used my code, last 24 years.

You ( Michael Moroney ) replied ( to me ):
> > One doesn't buy a Ferrai becuse it's "maintainable".
> 
> Irrelevant comparison. Whitespace and comments don't 
> slow code down in compiled languages.

Forget the compiler, whitespace and comments slow _me down.
When you see it, you know _immediately that the programmer is struggling.
I've posted _plenty of whitespace and comments here, by the way.

> > If whitespace and (borked) comments is what you need/like,
> > then add them yourself, later... _I don't want to see that crap.
> 
> Maybe you don't, but certainly the next guy who comes along to fix/improve/
> modernize it will.  Otherwise it may have the shelf life of a banana,
> once you have moved on/retired/died.

About a hundred thousand people have used my code, last 24 years.

[toc] | [prev] | [next] | [standalone]

#48214 — Re: About a hundred thousand people have used my code, last 24 years.

On Friday, 20 January 2017 06:57:10 UTC+2, Jeff-Relf.Me  wrote:
> You ( Michael Moroney ) replied ( to me ):
> > > One doesn't buy a Ferrai becuse it's "maintainable".
> > 
> > Irrelevant comparison. Whitespace and comments don't 
> > slow code down in compiled languages.
> 
> Forget the compiler, whitespace and comments slow _me down.
> When you see it, you know _immediately that the programmer is struggling.
> I've posted _plenty of whitespace and comments here, by the way.
> 
> > > If whitespace and (borked) comments is what you need/like,
> > > then add them yourself, later... _I don't want to see that crap.
> > 
> > Maybe you don't, but certainly the next guy who comes along to fix/improve/
> > modernize it will.  Otherwise it may have the shelf life of a banana,
> > once you have moved on/retired/died.
> 
> About a hundred thousand people have used my code, last 24 years.

After so long time and so lot of sad failures you are still under
Dunning–Kruger illusions? Don't be angry at us, other humans,
it is really not our fault.
 

[toc] | [prev] | [next] | [standalone]

#48215 — Re: How do you pronounce "Oo" ?

On Friday, 20 January 2017 10:41:35 UTC+2, Jeff-Relf.Me  wrote:
> How do you pronounce "Öö" ?  Is is Swedish ?

That vocal is present in lot of languages but several don't
use separate glyph for it. The pronunciation is drawn in 
dictionaries as əː  ... in English it is like "u" in "nurse" or
"turn" or "i" in "girl". The word means "night" in Estonian.

[toc] | [prev] | [next] | [standalone]

#48216 — Re: How pronounced is the 'r" ? is it long, like errr ?

On Friday, 20 January 2017 11:45:55 UTC+2, Jeff-Relf.Me  wrote:
> > > How do you pronounce "Öö" ?  Is is Swedish ?
> > 
> > in English it is like "u" in "nurse" or "turn"
> > or "i" in "girl". The word means "night" in Estonian.
> 
> How pronounced is the 'r" ? is Öö long, like errr ?

It is of longest degree of duration; one may elongate it as 
long as one wants to.

[toc] | [prev] | [next] | [standalone]

#48218

Michael Moroney wrote:
> Jeff-Relf.Me <@.> writes:
>
>>Michael Moroney wrote:
>>> professional coders write with future maintainability in mind.
>
>>One doesn't buy a Ferrai becuse it's "maintainable".
>
> Irrelevant comparison. Whitespace and comments don't slow code down in
> compiled languages.
>
>>If whitespace and (borked) comments is what you need/like,
>>then add them yourself, later... _I don't want to see that crap.
>
> Maybe you don't, but certainly the next guy who comes along to fix/improve/
> modernize it will.  Otherwise it may have the shelf life of a banana,
> once you have moved on/retired/died.

Even the original coder needs to be reminded how and why the
code was written the way it was.  Sometimes code was used
to provide services the hardware could not; later hardware
had been improved enough so that the code is no longer necessary.

There are many other reasons comments help the original developer;
another one is aging.

/BAH

[toc] | [prev] | [next] | [standalone]

#48219

jmfbahciv wrote:

> Michael Moroney wrote:
>>
>> Jeff-Relf.Me <@.> writes:
>>>
>>>If whitespace and (borked) comments is what you need/like,
>>>then add them yourself, later... _I don't want to see that crap.
>>
>> Maybe you don't, but certainly the next guy who comes along to fix/improve/
>> modernize it will.  Otherwise it may have the shelf life of a banana,
>> once you have moved on/retired/died.
>
>Even the original coder needs to be reminded how and why the
>code was written the way it was.  Sometimes code was used
>to provide services the hardware could not; later hardware
>had been improved enough so that the code is no longer necessary.
>
>There are many other reasons comments help the original developer;
>another one is aging.

You guys are not thinking from the perspective of a sociopath, like
Relf.

-- 
'Have you never heard someone say "There are too many things here I
cant decide"??!?!?'  -  "Culling Commitee" Chairman "Hadron" Quack

[toc] | [prev] | [next] | [standalone]

#48231

chrisv wrote:
> jmfbahciv wrote:
>
>> Michael Moroney wrote:
>>>
>>> Jeff-Relf.Me <@.> writes:
>>>>
>>>>If whitespace and (borked) comments is what you need/like,
>>>>then add them yourself, later... _I don't want to see that crap.
>>>
>>> Maybe you don't, but certainly the next guy who comes along to
fix/improve/
>>> modernize it will.  Otherwise it may have the shelf life of a banana,
>>> once you have moved on/retired/died.
>>
>>Even the original coder needs to be reminded how and why the
>>code was written the way it was.  Sometimes code was used
>>to provide services the hardware could not; later hardware
>>had been improved enough so that the code is no longer necessary.
>>
>>There are many other reasons comments help the original developer;
>>another one is aging.
>
> You guys are not thinking from the perspective of a sociopath, like
> Relf.

I'm speaking through him; I understand he won't learn.

/BAH

[toc] | [prev] | [next] | [standalone]

#48222

On 20/01/2017 13:39, jmfbahciv wrote:
> Michael Moroney wrote:
>> Jeff-Relf.Me <@.> writes:
>>
>>> Michael Moroney wrote:
>>>> professional coders write with future maintainability in mind.
>>
>>> One doesn't buy a Ferrai becuse it's "maintainable".
>>
>> Irrelevant comparison. Whitespace and comments don't slow code down in
>> compiled languages.
>>
>>> If whitespace and (borked) comments is what you need/like,
>>> then add them yourself, later... _I don't want to see that crap.
>>
>> Maybe you don't, but certainly the next guy who comes along to fix/improve/
>> modernize it will.  Otherwise it may have the shelf life of a banana,
>> once you have moved on/retired/died.
>
> Even the original coder needs to be reminded how and why the
> code was written the way it was.  Sometimes code was used
> to provide services the hardware could not; later hardware
> had been improved enough so that the code is no longer necessary.
>
> There are many other reasons comments help the original developer;
> another one is aging.
>
My favourite is that the comments tell you what it's supposed to do.

"self documenting code" includes any bugs.

Andy
--
... and I've plonked relf.

[toc] | [prev] | [next] | [standalone]

#48232

Vir Campestris wrote:
> On 20/01/2017 13:39, jmfbahciv wrote:
>> Michael Moroney wrote:
>>> Jeff-Relf.Me <@.> writes:
>>>
>>>> Michael Moroney wrote:
>>>>> professional coders write with future maintainability in mind.
>>>
>>>> One doesn't buy a Ferrai becuse it's "maintainable".
>>>
>>> Irrelevant comparison. Whitespace and comments don't slow code down in
>>> compiled languages.
>>>
>>>> If whitespace and (borked) comments is what you need/like,
>>>> then add them yourself, later... _I don't want to see that crap.
>>>
>>> Maybe you don't, but certainly the next guy who comes along to
fix/improve/
>>> modernize it will.  Otherwise it may have the shelf life of a banana,
>>> once you have moved on/retired/died.
>>
>> Even the original coder needs to be reminded how and why the
>> code was written the way it was.  Sometimes code was used
>> to provide services the hardware could not; later hardware
>> had been improved enough so that the code is no longer necessary.
>>
>> There are many other reasons comments help the original developer;
>> another one is aging.
>>
> My favourite is that the comments tell you what it's supposed to do.
>
> "self documenting code" includes any bugs.

Well, the only accurate documentation is the code.  In aulden times,
our formal documenation lagged hard/software shipments by 2 years.
So the only docs custumers received were the code sources, and
doc files along with beware files.  The beweare files documented
any last minute bugs, solutions or asspects discovered after
the distribution tapes had been made.

The comments which document what the code is supposed to do
is usually not kept up to date after years of development and
maintenance.  This can be very valuable if one is trying to
figure out what the original developer intended.

I really enjoy the ones which have comments indicating
"Thar be dragons"

/BAH

[toc] | [prev] | [next] | [standalone]

#48261

On 21/01/2017 14:08, jmfbahciv wrote:
> Well, the only accurate documentation is the code.  In aulden times,
> our formal documenation lagged hard/software shipments by 2 years.
> So the only docs custumers received were the code sources, and
> doc files along with beware files.  The beweare files documented
> any last minute bugs, solutions or asspects discovered after
> the distribution tapes had been made.
>
> The comments which document what the code is supposed to do
> is usually not kept up to date after years of development and
> maintenance.  This can be very valuable if one is trying to
> figure out what the original developer intended.
>
> I really enjoy the ones which have comments indicating
> "Thar be dragons"

In one sense the only accurate documentation is the code.

But in another sense- it's not documentation at all.

How can the code tell you "It might look as if you can optimise this 
out, but if you do XXXX will happen"?

Andy

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.c++

csiph-web