Re: [cc65] Calling another program: exec() ?

From: Groepaz <>
Date: 2011-01-24 13:45:06
On Montag 24 Januar 2011, you wrote:
> > Voting for a separate method for every
> > platform.
> I see - although not exactly the typical cc65 approach ;-))

my proposal would be having two functions:

1) load_exec() - which uses system specific ways to load and execute arbitrary 
binaries (ie not created by cc65) which are executable by standard ways of the 
system. this one would likely not to have to care about cc65 destructors or 
atexit or anything like that and instead do an i/o reset (restore vectors etc) 
by itself and then launch the external program. ie this is what one would use 
for making "menu" type of programs, filebrowsers etc.

2) one from the exec() family of functions, which should work as standard 
compliant as possible. this one then could be limited to calling cc65 created 
programs, which in turn means it could also deal with modules, making things 
like returning to the caller and passing arguments (and the mentioned file 
descriptors) to the callee possible (maybe).

having an exec() style function which tries to be both standard compliant and 
then tries to deal with launching arbitrary files seems a bit pointless to me 
to be honest, because it will end up with too much limitations in both ends.


If you look at scrollback and the last 30 lines are from you ... please shut 
<Moloch/Arkanix Labs>

To unsubscribe from the list send mail to with
the string "unsubscribe cc65" in the body(!) of the mail.
Received on Mon Jan 24 13:45:38 2011

This archive was generated by hypermail 2.1.8 : 2011-01-24 13:45:41 CET