Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!cs.utexas.edu!texbell!sugar!peter
From: peter@sugar.hackercorp.com (Peter da Silva)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Problem with CreateProc & LoadSeg
Message-ID: <5662@sugar.hackercorp.com>
Date: 6 May 90 16:00:53 GMT
References: <897@tau.sm.luth.se> <1856@dialog.sub.org>
Reply-To: peter@sugar.hackercorp.com (Peter da Silva)
Organization: Sugar Land Unix - Houston
Lines: 25

In article <1856@dialog.sub.org> root@dialog.sub.org (Christian Motz) writes
about C startup code waiting for a workbench message.
>    The "clean" way to circumvent this, I think, is to not  use  the  C
> startup code, i.e. _main(). This of course can be painful if you  like
> to use stdio stuff, but it works.

No, the clean way to do this is to send a workbench message. I published a
complete package for starting programs in this environment, under the name
"launch". Look for it at your nearest archive site.

If you don't do something like this the process will never get cleaned up
after, and you'll eat memory every time you run it.

Then you can add extra stuff you want to feed the program (like file handles)
after the message. This is pretty much how RogueStart works (which is something
else you should look into).

> How long can you get thrown in jail for doing something like that?

How long can you tread water?
-- 
 _--_|\  Peter da Silva <peter@sugar.hackercorp.com>.
/      \
\_.--._/ I haven't lost my mind, it's backed up on tape somewhere!
      v  "Have you hugged your wolf today?" `-_-'