Mail Archives: djgpp/2002/04/29/11:31:48
deckerben <deckerben AT freenet DOT de> wrote:
>> It's not "limited" to Win32 any more than DJGPP is limited to a DOS
>> environment. Win32 just *is* its environment.
> Uhhhh... limited... let's see here ... I take my DOS program and try in on
> Windows 3.1. Does it run? Yup. Not limited here.
> Win32 apps? Uhhhh... who did you say was limited?
You were using the word "limited" in two opposite meanings in a single
sentence, in your earlier posting. Cygwin definitely is not "limited
to Win32"; that's simply the platform it's meant for. Neither is it
limited _on_ Win32: it can access about the full set of features
offered for that platform.
The same two statements hold for DJGPP, but with respect to DOS as the
I was arguing mainly about the "limited on" part of it.
OTOH DJGPP definitely *is* limited on NT and its siblings, and also
(in other ways) on Windows 3.1 and 9x. Those limitations come either
as outright bugs in the DPMI services provided by those platforms, or
as sometimes hard-to-believe denial of service, like NT4 which doesn't
let a DOS app access long filenames, although the system itself
supports them quite nicely.
And of course, you plain and simply can't create a graphical Windows
app with DJGPP (RSXNTDJ doesn't count --- it's a separate project),
which is about as severe a limitation as one could possibly imagine,
for most people.
To sum it up: DJGPP and Cygwin serve similar purposes, but on strictly
different target platforms.
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.
- Raw text -