Re: Justifying Optimization

Joachim Durchholz <joachim_d@gmx.de>
11 Feb 2003 01:29:37 -0500

          From comp.compilers
Related articles
[15 earlier articles]
Re: Justifying Optimization lex@cc.gatech.edu (Lex Spoon) (2003-02-05)
Re: Justifying Optimization bobduff@shell01.TheWorld.com (Robert A Duff) (2003-02-05)
Re: Justifying Optimization vbdis@aol.com (2003-02-06)
Re: Justifying Optimization vbdis@aol.com (2003-02-06)
Re: Justifying Optimization joachim_d@gmx.de (Joachim Durchholz) (2003-02-11)
Re: Justifying Optimization joachim_d@gmx.de (Joachim Durchholz) (2003-02-11)
Re: Justifying Optimization joachim_d@gmx.de (Joachim Durchholz) (2003-02-11)
Re: Justifying Optimization bhurt@spnz.org (2003-02-11)
Re: Justifying Optimization nde_plume@ziplip.com (2003-02-11)
Re: Justifying Optimization cgweav@aol.com (2003-02-11)
Re: Justifying Optimization anton@mips.complang.tuwien.ac.at (2003-02-21)
| List of all articles for this month |
From: Joachim Durchholz <joachim_d@gmx.de>
Newsgroups: comp.compilers
Date: 11 Feb 2003 01:29:37 -0500
Organization: Compilers Central
References: 03-01-098 03-02-023
Keywords: optimize, practice
Posted-Date: 11 Feb 2003 01:29:37 EST

VBDis wrote:
>
> Did you never ask for better development tools, or programming
> languages, which reveal such bugs on the very first compilation of the
> code?


You can't switch tools in mid-project. Asking for a different tools
would have been ridiculous. It's even difficult to switch tools
between projects. The cost for retraining the programmers can easily
outweigh any gains in productivity for years to come. Particularly if
the new toolset meets resistance or incompetence on the side of the
programmers.


Regards,
Joachim

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.