Mail Archives: djgpp/2000/03/22/16:12:18
Eli Zaretskii wrote:
> I doubt that 10 seconds would be enough to correct an error, at least
> not in most cases.
>
> Anyway, if you use the right tools, you can start correcting the
> errors without waiting for the compiler to finish.
Yes, but I can't start recompiling until the other compilation finishes.
At least I can't in the specific setup I'm using...
> > The point being, if my code doesn't compile in < 2 seconds, I
> > look for ways to speed it up. I realize that, beyond some limit,
> > there is nothing I can do, and if most of the time is spent in the
> > linker stage, there's not much I can do, but 10 seconds is a long
> > time for most of us.
>
> Please note that 10 seconds is what it should take for a 10,000-line
> source to compile. Anyone who writes such long source files has *got*
> to be prepared to wait for the compiler.
Or to split it up in to smaller chunks and use 'make' without the '-k'
option.
> Most files of a _reasonable_ size will indeed compile in less than 2
> seconds, even on a P166.
And that's precisely why I'm spoiled (most of my code compiles so damn
fast under djgpp, I don't even see the boxes pop up in rhide).
I think of a compiler as a tool that helps me write code, not just makes
the executable.
--
(\/) Rolf Campbell (\/)
- Raw text -