Date: Thu, 20 Mar 1997 13:52:04 -0700 From: Warner Losh <imp@village.org> To: Terry Lambert <terry@lambert.org> Cc: james@wgold.demon.co.uk, hackers@freebsd.org Subject: Re: Barb problem, FOUND Message-ID: <E0w7oof-0003K9-00@rover.village.org> In-Reply-To: Your message of "Thu, 20 Mar 1997 13:33:53 MST." <199703202033.NAA29840@phaeton.artisoft.com> References: <199703202033.NAA29840@phaeton.artisoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199703202033.NAA29840@phaeton.artisoft.com> Terry Lambert writes: : > : The argument is without merit: if a compiler is buggy, it should be : > : fixed, or the vendor should be forced out of business by word of mouth. : > : > That's a very high and noble attitude, but sadly products have to be : > shipped and often times you are't in the position to be able to fix a : > vendor's product *NOW*. : : Ditch your vendor. Eventually he will fix it for loss of business : over the problem, or he will disappear for loss of business over : the problem. Either way, the vendor is not a long term issue for : this kind of problem. At the time we were doing OI, nearly *ALL* of the compilers were so afflicated. Sun's, Centerline's, Lucid's, cfront, Microsoft's, Dec's, HP's and IBM's. They all sucked at doing inline virtuals, creating multiple copies for them. There were *NO* compilers that we could have used that were compainle with the Sun compiler on SunOS (our primary market for this library). Oh, and g++ wouldn't even compile OI. When all or nearly all of the compilers you have to deal with don't grok a construct, it is a bad construct. Sometimes it isn't as simple as you paint thing Terry. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E0w7oof-0003K9-00>