Mail Archives: djgpp/2000/06/12/11:00:23
> You cannot ``prove'' this once and for all. As GCC is developed, new code is
> constantly added to it. If this new code looks too similar to copyrighted
> software...
Yet this is a problem faced by all so-called "open-source" projects. Is this
also a problem in programs such as Apache and Netscape? Did the Netscape crew
shrink the browser's memory footprint so it wouldn't seem like they had ripped
of Microsoft? (hehe, that one's a joke).
> > I don't want to start arguing about Watcom vs. GCC, but I will defend it
when I
> > feel the need arises.
>
> I fail to see why do you think you need to defend it. Nobody is attacking
> Watcom here.
>
> > Watcom's not such a bad product (and it's originally
> > Canadian, like me ;) So it's more a matter of pride.
>
> This forum is not about national pride, it's about other issues.
Heh heh, it was a joke. Sort of. Anyway, what I mean is that when I see
someone knocking Watcom, I will try to correct that person as best I can (case
in point: Damian's readme 3rd from many moons ago). People seem to think that
you can only use one or the other, and that the one you are using is invariably
better than the other. I use Watcom and GCC all the time, sometimes one is
better suited than another. I prefer Watcom's Windows/NT support over using
one of the GCC ports for that platform. But this is all irrelevent, and is not
contributing to GCC/DJGPP that much.
AndrewJ
- Raw text -