Date:	Thu, 6 Feb 92 09:14:46 EST
From:	csa AT pennies DOT sw DOT stratus DOT com (Chris Arthur)
To:	dj AT ctron DOT com
Subject:	Re: Reasons not to use DJGPP :-)
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu
Status:	O

There are some things I was going to suggest for addition to go32;
if you're working on 2.0, I guess now is a good time to bring them
up...

It would be nice if go32 could detect when another copy of itself (of
the same version) was already in memory, so you wouldn't have to have
as many as 3 or 4 of them loaded at once (say, demacs running a 32-bit
GNU make running gcc (I know, gcc.exe is 16-bit) running cc1, and
there are probably worse cases)...then, if you were going to do that,
it would be nice to be able to just load go32 as a tsr, and have it
automatically used by a stub-linked 32-bit program (ie, cc1 with
stub.exe would load, see that go32 was in memory, and just call it);
this would probably make the programs start a little faster...then, if
a single copy of go32 handles all 32-bit programs currently loaded
(maybe inactive while waiting on another program), perhaps it could
avoid swapping out all of one program to run another (ie, say you run
a 32-bit program from demacs; it would leave most of demacs paged in
unless and until the child process needed the space)...all of this may
already be part of the multitasking stuff you had mentioned, but I
thought I'd suggest it just in case.

also, what are the plans for gdb support?  You had said a while ago
that you were waiting until you got multitasking into go32; once that's
there, are you planning to do gdb?

						chris

- Raw text -