| Related articles |
|---|
| [16 earlier articles] |
| Re: Speedy compilers jeff-news@jeff-jackson.com (Jeff Jackson) (1998-12-18) |
| Re: Speedy compilers albaugh@agames.com (1998-12-19) |
| Re: Speedy compilers terryg@uswest.net (1998-12-19) |
| Re: Speedy compilers genew@vip.net (1998-12-19) |
| Re: Speedy compilers fjh@cs.mu.OZ.AU (1998-12-19) |
| Re: Speedy compilers rweaver@ix.netcom.com (1998-12-19) |
| Re: Speedy compilers zalman@netcom.com (1998-12-19) |
| From: | zalman@netcom.com (Zalman Stern) |
| Newsgroups: | comp.compilers |
| Date: | 19 Dec 1998 22:15:37 -0500 |
| Organization: | ICGNetcom |
| References: | 98-11-047 98-11-086 98-11-089 98-12-040 98-12-052 |
| Keywords: | practice |
: [I think the message here is that compilers that work are preferable to
: compilers that don't. -John]
And:
Try to make debugging features and optimization features as orthogonal
as possible so both can be used at the same time. Yes I realize that
is a hard problem, but as a developer, I'm willing to accept
compromise. For example, I can deal with the fact that the code I'm
trying to debug doesn't exist because it was optimized away so long as
the debugger gives me a concrete notion that this is the case. Often
the debugger just applies breakpoints to different pieces of code
instead of what I pointed at, etc.
-Z-
Return to the
comp.compilers page.
Search the
comp.compilers archives again.