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

Groups > comp.lang.c++ > #48232

Re: Whitespace and (borked) comments.

Cross-posted to 3 groups.

Show all headers | View raw

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

Back to comp.lang.c++ | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

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

csiph-web