Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Whitespace and (borked) comments.
81 views
Skip to first unread message
Jeff-Relf.Me
Jan 19, 2017, 5:24:11 AM1/19/17
to
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.
> 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.
Peter Köhlmann
Jan 19, 2017, 5:30:58 AM1/19/17
to
wrote:
Idiot
chrisv
Jan 19, 2017, 8:29:58 AM1/19/17
to
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"
> Relf wrote:
>>
>> Michael Moroney wrote:
>>>
>>> professional coders write with future maintainability in mind.
>>
>> One doesn't buy a Ferrai becuse it's "maintainable".
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
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"
Jerry Stuckle
Jan 19, 2017, 10:36:37 AM1/19/17
to
--
==================
Remove the "x" from my email address
Jerry Stuckle
jstu...@attglobal.net
==================
Peter Köhlmann
Jan 19, 2017, 10:48:37 AM1/19/17
to
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
> 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?
>
like that Relf imbecile. But for the lack of better words to describe that
dimbulb...
woodb...@gmail.com
Jan 19, 2017, 12:58:30 PM1/19/17
to
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
Please don't swear here.
Brian
Ebenezer Enterprises - In G-d we trust.
http://webEbenezer.net
GreyCloud
Jan 19, 2017, 1:20:47 PM1/19/17
to
written and for what.
red floyd
Jan 19, 2017, 4:25:25 PM1/19/17
to
On 1/19/2017 9:58 AM, woodb...@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.
> On Thursday, January 19, 2017 at 7:29:58 AM UTC-6, chrisv wrote:
>
>
> Please don't swear here.
>
Michael Moroney
Jan 19, 2017, 11:26:58 PM1/19/17
to
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
>Michael Moroney wrote:
>> professional coders write with future maintainability in mind.
>One doesn't buy a Ferrai becuse it's "maintainable".
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.
modernize it will. Otherwise it may have the shelf life of a banana,
once you have moved on/retired/died.
Jeff-Relf.Me
Jan 19, 2017, 11:57:10 PM1/19/17
to
You ( Michael Moroney ) replied ( to me ):
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.
> > 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.
>
> Irrelevant comparison. Whitespace and comments don't
> slow code down in compiled languages.
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.
Öö Tiib
Jan 20, 2017, 3:17:26 AM1/20/17
to
Dunning–Kruger illusions? Don't be angry at us, other humans,
it is really not our fault.
Jeff-Relf.Me
Jan 20, 2017, 3:41:35 AM1/20/17
to
How do you pronounce "Öö" ? Is is Swedish ?
Öö Tiib
Jan 20, 2017, 3:57:43 AM1/20/17
to
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
> How do you pronounce "Öö" ? Is is Swedish ?
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.
Jeff-Relf.Me
Jan 20, 2017, 4:45:55 AM1/20/17
to
> > 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 ?
Öö Tiib
Jan 20, 2017, 6:50:30 AM1/20/17
to
long as one wants to.
jmfbahciv
Jan 20, 2017, 8:40:09 AM1/20/17
to
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
chrisv
Jan 20, 2017, 8:47:01 AM1/20/17
to
Relf.
--
'Have you never heard someone say "There are too many things here I
cant decide"??!?!?' - "Culling Commitee" Chairman "Hadron" Quack
Vir Campestris
Jan 20, 2017, 5:02:18 PM1/20/17
to
"self documenting code" includes any bugs.
Andy
--
... and I've plonked relf.
jmfbahciv
Jan 21, 2017, 9:08:53 AM1/21/17
to
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.
> 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.
/BAH
jmfbahciv
Jan 21, 2017, 9:08:53 AM1/21/17
to
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
Vir Campestris
Jan 22, 2017, 12:58:54 PM1/22/17
to
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.
> 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"
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
0 new messages