Mail Archives: djgpp/1993/06/01/13:58:29
> processes, and run the child. What you wind up with is shared code and
> shared global data, but separate auto data. The child also inherits a
> copy of the first 16 words of the parents arglist. As long as the child
> behaves itself, the parent survives.
That's pretty much vfork in a nutshell.
> DJ, am I allowed to look at BSD code if I intend to give this to you to
> include in future releases, or will I become "unclean"?
Most of libc.a is based on the free'd BSD sources. Just make sure
it's the freed ones you're looking at, or we'll all have to pay AT&T
royalties. Anything marked "public domain" or including an "as-is"
type copyright is OK for djgpp. The problem is when GPL code is used
in such a way that it causes applications built by djgpp to become
GPL. This has a habit of discouraging djgpp use for commercial
applications.
- Raw text -