home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.programmer
- Path: sparky!uunet!mcsun!chsun!bernina!wild
- From: wild@nessie.cs.id.ethz.ch (Markus Wild)
- Subject: Re: running segments from within an application
- Message-ID: <1992Nov7.141904.15440@bernina.ethz.ch>
- Sender: news@bernina.ethz.ch (USENET News System)
- Organization: Swiss Federal Institute of Technology (ETH), Zurich, CH
- References: <9211050408.AA24272@mackay.mpce.mq.edu.au> <36744@cbmvax.commodore.com> <10018@cbmger.de.so.commodore.com>
- Date: Sat, 7 Nov 1992 14:19:04 GMT
- Lines: 18
-
- In article <10018@cbmger.de.so.commodore.com> peterk@cbmger.de.so.commodore.com (Dr Peter Kittel Germany) writes:
- >In article <36744@cbmvax.commodore.com> jesup@cbmvax.commodore.com (Randell Jesup) writes:
- > >really safe way. The problem is that there are two separate ways in which
- > >arguments are passed (well actually 3): 1) pointer to string in a0, length in
- > >d0, string usually has a \n in it at the end. 2) as buffered input on the
- > >input filehandle (RunCommand does this for you). 3) via Set/GetArguments()
- > >(also done for you by RunCommand).
- >
- >And how about 4) via a normal file in RAM DISK: ?
-
- Hm.. 4 sounds just as custom as 5) via the stack, as execve() passes
- argc, argv, environ to ixemul-children;-)
-
- -Markus
- --
- Markus M. Wild - wild@nessie.cs.id.ethz.ch | wild@amiga.physik.unizh.ch
- Vital papers will demonstrate their vitality by spontaneously moving
- from where you left them to where you can't find them.
-