#Visual C++ CD ROM
2 messages in this thread
Mike,
Thanks for the information and the clarification.
As far at the optimization issue is concerned – I realize that it is a very
complicated issue, I brought this up only as an illustration of what could be
done. My comments concerning multi-thread capabilities were not intended to be
restricted to optimization. Having one thread doing pre-compiles while another
is doing compiles sans optimization is still a very valid idea. I recognize
that simply adding multi-thread capabilities is not the panacea for everthing,
but such capabilities could surely be leveraged to a much greater extent than
they currently are for many products – C compilers included.
I don't know of any compilers which do this either, on the other hand I don't
know of any operating systems which are as ready and capable for something like
this as NT is.
Joe
There is 1 Reply.
Actually optimization is one of the best candidates for exploiting multi-thread
capabilities. The majority of optimizations are localized within
procedures/blocks and as such can be performed independent of other activity
with very little effort.
I would rather that more work were spent on the "active compiler" approach.
While color-coded syntax is a trivial first step, a full blown approach that
would identify semantic errors as they are typed would provide a significant
improvement in the code-writing stage.