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

Groups > sci.physics > #610066 > unrolled thread

Re: My code is dense, and hard to read, like the Washington Post.

Back to article view | Back to sci.physics

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

  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

Page 2 of 2 — ← Prev page 1 [2]

#610150 — Someday, if you're lucky, you'll know the freedoms I enjoy.

I have a 4K IPS arm-mounted monitor, swung over my bed;
so, unlike cell phone users, I enjoy 236 columns of text.
How I use the white space is up to _me_, and it varies.

"Michael Moroney and gang" aren't paying me -- couldn't pay me;
so they have no say in the matter.
Someday, if they're lucky, they'll know the freedoms I enjoy.

When/while debugging a problem area,
I might use a lot of white space... including comments;
othewise, not so much.

From X.CPP in "Jeff-Relf.Me/X.ZIP", here's some 
"random" (to you) code I wrote/modified today,
with the actual, unmodified WhiteSpace/LineLengths
( with some added comments ):

  float  DaysAgo, Oldest = 0 ; int  cnt_MIDs = Ls.PP - Ls.BB + 1 ;  LsA B_MIDs, E_MIDs ;
  E_MIDs = B_MIDs = ( LsA ) MallocTmp( rv = cnt_MIDs * szPtr );
  memmove( B_MIDs, Ls.BB, rv ); E_MIDs += cnt_MIDs ;
  Sort_MIDs_by_ASCII( B_MIDs, E_MIDs - 1 ), Sort_Posts_by_Recent( Ls.BB, Ls.PP );
  const int TooManyPerDay = 5, minPostingSpan = 7, mxAge = 32 ; 

  //  Expire old Posts.  Count how many times a nym used a "BadRig".
  { LoopXx( Ls, Ls ) { List_T &Msg = *P ;  NymT &Nym = *Msg.Nym, &Rig = *Msg.Rig, &Ser = *Msg.Ser, &Sbj = *Msg.Sbj ;
      if ( DaysAgo = Msg.DaysAgo, DaysAgo >= mxAge ) { Msg.Expired = Msg.Reddit = 1 ;  continue ;  }
      if ( Msg.ID = ++Nym.Cnt, Rig.Cnt++, Ser.Cnt++, Sbj.Cnt++, !Nym.hardRank && !Nym.Dropped ) Nym.CntBadRigs += Rig.Dropped || Ser.Dropped ;
      if ( DaysAgo > Oldest ) Oldest = DaysAgo ;   if ( DaysAgo < Nym.Newest ) Nym.Newest = DaysAgo ;  if ( DaysAgo > Nym.Oldest ) Nym.Oldest = DaysAgo ;
      if ( DaysAgo < Rig.Newest ) Rig.Newest = DaysAgo ;   if ( DaysAgo > Rig.Oldest ) Rig.Oldest = DaysAgo ;   if ( DaysAgo < Ser.Newest ) Ser.Newest = DaysAgo ;
      if ( DaysAgo > Ser.Oldest ) Ser.Oldest = DaysAgo ;   if ( DaysAgo < Sbj.Newest ) Sbj.Newest = DaysAgo ;   if ( DaysAgo > Sbj.Oldest ) Sbj.Oldest = DaysAgo ;  } }

  //  Expire old Nyms.  "Reddit Drop" (untrusted) nyms that _always_ use a "BadRig".
  { LoopXx( Nm, Nm ) { NymT &Nym = *P ;   if ( !Nym.Cnt ) { Nym.Expired = 1 ;  continue ;  }   Nym.Dropped |= Nym.CntBadRigs == Nym.Cnt ;  } }

  //  (Re)Build all "References:" lines ( using a binary search ).  Flag direct/indirect relpies to "(R)" nyms ( e.g. "JeffRelf(R)" ).
  { LoopXx( Ls, Ls ) { List_T &Msg = *P ;   if ( Msg.Expired ) continue ;   NymT &Nym = *Msg.Nym ;   Nym⁺mID_T  *pLX = &Msg.H.L0 ; int ReplyDepth = 0 ;
    { Loop( mxDepth ) { Nym⁺mID_T  &Parent_Nym⁺mID = *--pLX ;  if ( !Parent_Nym⁺mID.MID ) break ;
        LsA BB = B_MIDs, PP = BB, EE = E_MIDs ;  LsP  P, Parent = 0 ; int X ;
        Find:    if ( BB >= E_MIDs ) goto New ;
        PP = BB + ( EE - BB ) / 2, P = *PP, X = strCmp( P->H.L0.MID, Parent_Nym⁺mID.MID );
        if ( X > 0 ) { if ( BB = ++PP, BB > EE ) goto New ;  goto Find ;  }
        if ( X < 0 ) { if ( EE = --PP, EE < BB ) goto New ;  goto Find ;  }
        if ( Parent = P, !Parent_Nym⁺mID.Nym ) Parent_Nym⁺mID.Nym = Parent->Nym->Name ;
        New:    if ( Msg.Cat == Cat_Mid && ReplyDepth != cMe && gMeOrMine( Parent_Nym⁺mID  ) ) ReplyDepth = vMeOrMine ;  Msg.Elders[ Msg.cnt_Ances++ ] = Parent ;
        if ( !Msg.FromDisk && J < mxDepth - 1 && Parent && Parent->H.L1.MID ) pLX[-1] = Parent->H.L1 ;  } }

    if ( !Msg.Reddit && ReplyDepth ) Msg.ToMeOrDeepMine = 1, Msg.Cat = Cat_Top, Nym.Special = !Nym.Dropped ;  } }

  //  Flag/Count "Kids" and "Visitors/NymShifters".
  int cntDropped, cntKids, cntAdults, cntVisitors ;  cntDropped = cntKids = cntAdults = cntVisitors = 0 ;
  { LoopXx( Nm, Nm ) { NymT &Nym = *P ;   if ( Nym.Expired ) continue ;   Nym.Regular = Nym.Oldest - Nym.Newest >= minPostingSpan ;
      if ( Nym.PostsPerDay = Nym.Cnt / ( 1 + Nym.Oldest ), !Nym.hardRank && !Nym.Dropped ) !Nym.Regular ? ( Nym.Visitor = 1 ) : Nym.PostsPerDay <= TooManyPerDay ? ( Nym.Adult = 1 ) : ( Nym.Kid = 1 );
      cntDropped += Nym.Dropped, cntKids += Nym.Kid, Nym.Adult ? cntAdults++ : !Nym.Regular ? cntVisitors++ : 0 ;  } }

  //  Limit "Kids" and "Visitors/NymShifters" to their 5 most recent posts, last 24 hours.  "Reddit Drop".
  { LoopXx( Ls, Ls ) { List_T &Msg = *P ;   if ( Msg.Expired ) continue ;   NymT &Nym = *Msg.Nym ;
      if ( !Msg.Reddit && !Msg.ToMeOrDeepMine && !Nym.Special && ( Nym.Dropped || !Nym.Adult && ( Msg.DaysAgo >= 1 || Nym.cnt_unReads >= 5  ) ) ) Msg.Reddit = 1 ;
      Nym.Expired ? ( Msg.Expired = 1 ) : !Msg.Reddit ? Nym.cnt_unReads++ : ( Msg.Minimal = !Nym.Me || Msg.ID > 9 );  } }

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

#610181

On 12/23/16 06:54, chrisv wrote:
> Michael Moroney wrote:
>
>> Jeff-Relf.Me<@.>  writes:
>>
>>> I'll tell you ( yet again ) what I told them:
>>
>>>   My code is dense, and hard to read, like the Washington Post;
>>>   sorry, but it's _not_ like an advert, or comic strip,
>>>   with lots of graphics, big fonts, color and WhiteSpace.
>
> How ironic, from someone who posts HTML to USENET.
>
>>> I won the day; I retained control; I get paid -- They lost.
>
> You're a sociopath.

Says the pot.

>
>> Peer code review works very well here. Sometimes a bug gets
>> found the original author missed.  The maintainability/
>> legibility get checked if necessarily, since it is
>> expected that someday, someone else (perhaps one of them)
>> may have to maintain it.
>>
>> "Dense code" is for executable files, the output of compilers
>> and linkers.  Source code exists for humans as few humans
>> ever write in the machine language of the target computer,
>> humans use computer languages.
>>
>> Again, code for your own use or one-offs that aren't part
>> of the product can be anything, but professional coders
>> write with future maintainability in mind.
>
> He's had all this explained before.  You may as well be talking to a
> brick wall.
>

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

#614043 — 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] | [prev] | [next] | [standalone]

#614045 — Re: Whitespace and (borked) comments.

 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]

#614063 — Re: Whitespace and (borked) comments.

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]

#614080 — Re: Whitespace and (borked) comments.

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]

#614083 — Re: Whitespace and (borked) comments.

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]

#614110 — Re: Whitespace and (borked) comments.

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]

#614144 — Re: Whitespace and (borked) comments.

On 1/19/2017 1:20 PM, GreyCloud wrote:
> 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.
> 

What follow-up coders?  No one with any self respect would touch his
code.  But that's OK, because anyone who knows the least bit about
coding would never hire him in the first place.

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

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

#614232 — Re: Whitespace and (borked) comments.

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]

#614239 — 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]

#614279 — Re: Whitespace and (borked) comments.

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]

#614280 — Re: Whitespace and (borked) comments.

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]

#614562 — Re: Whitespace and (borked) comments.

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]

#614399 — Re: Whitespace and (borked) comments.

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]

#614465 — Re: Whitespace and (borked) comments.

I've got a new way to play poker; naming

've plonked r

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

#614563 — Re: Whitespace and (borked) comments.

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]

#614743 — Re: Whitespace and (borked) comments.

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]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | sci.physics

csiph-web