Re: CW X 10.1++ ... let's start a pool

>> CodeWarrior IDE without the plugins is just another IDE there are
>> many of them around. CodeWarriors power was in the compiler
>> technology, debugger technology and linker technology and
>> bringing it all together to form a cohesive bond.

I don't know if I would agree with that fully. If it were "just
another IDE", I doubt i would be having the trouble moving to Xcode as
I do. I agree that the compiler technologies were great, but frankly,
if forced I'd rather have the CodeWarrior IDE containing the Xcode
compilers than vice-versa.

Don't get me wrong, I think the CW compiler and debugger are much nicer
than Xcode's (gcc has awful diagnostics and warning/error
descriptions). It's just that now that Metrowerks has stupidly sold
off the very x86 compiler that could have saved its ***, only the IDE
is left.

My best case scenario (admittedly, not likely to happen):

1. Metrowerks at the last moment releases the source code to the
CodeWarrior IDE.
2. Some enterprising individual modifies and recompiles the IDE so that
it can be built on Xcode as a Universal Binary.
3. Yet another enterprising individual wraps the gcc x86 Mac compiler
as a CodeWarrior compiler plugin using Metrowerks' public API. Thus CW
can now create programs binary-compatible with Xcode.
4. CodeWarrior can once again build itself, thus "eating its own dog
food".

Hey, I can dream, can't I?

.

Loading