Re: [64-bit Delphi] A msg from Hairy (van Tassel)

From: Nick Hodges [TeamB] (nickhodges_at_gmail.com)
Date: 03/18/05 

Date: 18 Mar 2005 06:33:51 -0800

BaSS wrote:

>
> I've been around for 2 weeks now, and almost EVERY post where someone
> argues that the product might be inperfect gets bombed by at least 2
> TeamB members telling the poster he's got it all wrong, automatically
> resulting in discussions like the one above..

Sorry, Dude, but you are wrong. ;-)

It sure would be nice if people would actually /read/ what we say
instead of ranting and whining about things we don't say.

Here's the /entire/ point of contention: The claim was made that the
Update to D7 introduced bugs in the compiler. I dispute this claim,
because, well, it's false. No one yet has been able to point to a bug
in the D7 Update compiler.

Danny /did/ say that fixes in the updated compiler removed certain
optimizations, but the removal of optimizations is /not/ a bug, despite
the childish mockings of others here.

/No one/ has said that the loss of optimizations isn't unfortunate. It
is. But to go around saying that the compiler in the D7 update is
"unusable" and "buggy" is utterly ridiculous and a pile of horse manure.

The problem is further exacerbated by people's inability to understand
what a bug is and what "working as designed" means. These folks seem
to think people who /do/ understand the are risible. Oh well, I need
not feel bad for understanding the difference.

Of course, there are those who simply want to pule and complain, and
will quarter no correction on the inaccuracies of their pulings. 

-- 
Nick Hodges -- TeamB
Lemanix Corporation -- http://www.lemanix.com
Read my Blog -- http://www.lemanix.com/nick

Relevant Pages

  • Re: /Od compiler option problem
    ... >> found out that when I had the compiler option /Od set the project would ... >> work properly but when it was not set the bug would appear. ... > When optimizations are enabled the compiler may do those things and more. ... > declare success again or you can try to find the cause. ...
    (microsoft.public.dotnet.languages.vc)
  • Re: /Od compiler option problem
    ... > work properly but when it was not set the bug would appear. ... /Od means "disable the optimizing compiler". ... It is important to disable optimizations while ... declare success again or you can try to find the cause. ...
    (microsoft.public.dotnet.languages.vc)
  • Re: large files: when ubiquitous?
    ... I was merely pointing out that the compiler cannot ... > it should NEVER make optimizations that assume that it has unique ... > Then it's a bug. ... >> to a char pointer type or changing p to be a char ...
    (comp.os.linux.development.system)
  • Re: [64-bit Delphi] A msg from Hairy (van Tassel)
    ... optimizations, ... indicates that it is a bug in the compiler, and that it's not just a ... an update, and suddenly the lines go all over the place, crossing each ... You wouldn't label that as a bug? ...
    (borland.public.delphi.non-technical)
  • Re: WaitForSingleObject() will not deadlock
    ... One is to hijack the semantics of volatile to disable compiler optimizations ... and otherwise let the compiler to agressive optimization. ... Agressive optimizations are the ones that work on the edge of the semantics of the ... Because the compiler can see into lock and unlock, it is able to reduce f ...
    (microsoft.public.vc.mfc)