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

Groups > sci.physics > #614563

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 sci.physics | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Re: My code is dense, and hard to read, like the Washington Post. moroney@world.std.spaamtrap.com (Michael Moroney) - 2016-12-22 21:22 +0000
  Re: My code is dense, and hard to read, like the Washington Post. chrisv <chrisv@nospam.invalid> - 2016-12-23 07:54 -0600
    Re: My code is dense, and hard to read, like the Washington Post. flatfish+++ <flatfish@linuxmail.org> - 2016-12-23 09:35 -0500
      Re: My code is dense, and hard to read, like the Washington Post. moroney@world.std.spaamtrap.com (Michael Moroney) - 2016-12-23 16:21 +0000
        My code is dense, and hard to read, like the Washington Post. Jeff-Relf.Me <@.> - 2016-12-23 08:52 -0800
          Re: My code is dense, and hard to read, like the Washington Post. moroney@world.std.spaamtrap.com (Michael Moroney) - 2016-12-23 19:12 +0000
            Re: My code is dense, and hard to read, like the Washington Post. chrisv <chrisv@nospam.invalid> - 2016-12-23 13:27 -0600
              Re: My code is dense, and hard to read, like the Washington Post. Peter Köhlmann <peter-koehlmann@t-online.de> - 2016-12-23 20:56 +0100
                Re: My code is dense, and hard to read, like the Washington Post. Snit <usenet@gallopinginsanity.com> - 2016-12-23 13:32 -0700
                Re: My code is dense, and hard to read, like the Washington Post. Peter Köhlmann <peter-koehlmann@t-online.de> - 2016-12-23 22:40 +0100
                Re: My code is dense, and hard to read, like the Washington Post. Snit <usenet@gallopinginsanity.com> - 2016-12-23 15:19 -0700
                My C++ Coding Standards ( apologies to Bjarne Stroustrup ). Jeff-Relf.Me <@.> - 2016-12-23 17:06 -0800
                Re: My C++ Coding Standards ( apologies to Bjarne Stroustrup ). Peter Köhlmann <peter-koehlmann@t-online.de> - 2016-12-24 10:40 +0100
                Re: My code is dense, and hard to read, like the Washington Post. jmfbahciv <See.above@aol.com> - 2016-12-24 14:04 +0000
        I explain each of the warnings I disable, and why. Jeff-Relf.Me <@.> - 2017-01-19 03:00 -0800
          Re: I explain each of the warnings I disable, and why. Peter Köhlmann <peter-koehlmann@t-online.de> - 2017-01-19 12:09 +0100
          Re: I explain each of the warnings I disable, and why. moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-20 04:29 +0000
            Re: I explain each of the warnings I disable, and why. chrisv <chrisv@nospam.invalid> - 2017-01-20 06:48 -0600
              Re: I explain each of the warnings I disable, and why. Peter Köhlmann <peter-koehlmann@t-online.de> - 2017-01-20 16:52 +0100
      It's fucking email ! ! Jeff-Relf.Me <@.> - 2017-01-19 02:53 -0800
    Someday, if you're lucky, you'll know the freedoms I enjoy. Jeff-Relf.Me <@.> - 2016-12-23 08:05 -0800
    Re: My code is dense, and hard to read, like the Washington Post. GreyCloud <mist@cumulus.com> - 2016-12-23 13:49 -0700
  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. 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. Jerry Stuckle <jstucklex@attglobal.net> - 2017-01-19 14:49 -0500
    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: 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. noTthaTguY <abu.kuanysh05@gmail.com> - 2017-01-20 18:31 -0800
          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