Mail Archives: djgpp/2000/06/03/20:15:21
> If you really want to discuss this, there are appropriate forums for
> this (e.g., gnu.misc.discuss), where you can find people who know more
> about this.
Nah... I was just curious. Besides, you seem to know the answer to just about
everything else. ;)
> One assumption that you make and that I'm not sure is true, is that
> the success you mention came so easily. It could be that this success
> requires them to keep fighting every day.
Hmm... what I meant was that by now they've proven that the compiler is their
own work. If they make it smaller and better now, who's going to care? You
said they made it big so no one would think they'd been "plagiarised", by now
that has been proven.
> These are all x86-based. GCC supports lots of non-Intel CPUs (in
> fact, it took Linux to get the GCC to respect x86 as an important
> platform).
- did you read the paragraph after it? -
It doesn't match GCC in scope of host platforms or target architechtures, but
no compiler I know of can target as many x86's operating systems as Watcom all
in one package (that excludes the myriad number of ports of GCC from this
comparison).
- meaning out of the box, one compiler supports all what I listed before -
I don't want to start arguing about Watcom vs. GCC, but I will defend it when I
feel the need arises. Watcom's not such a bad product (and it's originally
Canadian, like me ;) So it's more a matter of pride.
- OTO, this is all moot, off-topic, and irrelevent. -
Andrew J
- Raw text -