Mail Archives: djgpp/2004/05/27/04:30:10.1
"Eli Zaretskii" <eliz AT gnu DOT org> wrote in message news:<2719-Sun23May2004185224+0300-eliz AT gnu DOT org>...
> > From: 048321887-0001 AT t-online DOT de (Udo Kuhnt)
> > Newsgroups: comp.os.msdos.djgpp
> > Date: 23 May 2004 06:27:29 -0700
> >
> > If a file had been opened by the parent process, it should also be open for
> > the child process which can access it using the same handle. If the child
> > closes the file in its VM using the handle, it will still be open in the
> > parent's VM.
That is probably the reason why the task manager in DR-DOS requires SHARE to
be loaded, but requiring SHARE is hardly a problem in this case.
> And the latter means that just copying is not good: it is a frequent
> case that the child closes one or more of inherited handles that it
> doesn't need. You don't want that to invalidate the handle in the
> parent, since existing programs don't expect such a calamity.
It is not invalidated because each VM has its own set of file structures.
> Se perhaps writing a (16-bit real-mode) program to test this aspect
> would be a useful first step.
??? I do not see the point - DJGPP cannot produce such executables, and using
a different compiler would make the result harder to interpret. Besides, the
MT API in DR-DOS calls for a 32-bit implementation, so using a 16-bit test
program would probably not work anyway.
- Raw text -