1. Program overlays
I'm at a point right now where a certain feature of Euphoria could be very
useful if it existed.
Right now, if I want to run a different Euphoria program from within my Euphoria
program, I need to use system_exec("exw..... This requires a second interpreter
to be opened, with a separate shell, separate console, etc. And if I want to
pass full control over to the second program, I can't. I have to add an abort(1)
statement after this line to release the current program. This all works as far
as it goes, but it's not very elegant.
What I would like to see (I think it's been mentioned before) is something like
the following:
run_euphoria("Myprog2.ex","param1 param2 param3")
The interpreter would, upon processing this line, run the same cleanup routine
internally that abort() uses, but instead of terminating the interpreter,
re-initialize it with the new program and command-line options (second parameter
in the routine call).
I'd love to see a call_euphoria(...) routine where control returns to the
original calling program upon termination of the called program, but I imagine
that would be more complex and too hard to maintain. I'd be happy with just the
first one.
If Rob has any religious objections to a run_euphoria statement, I suppose I
could continue to kludge along unelegantly 
. I'd also like to get some
feedback from others whether or not they would find this kind of functionality
useful. If it's just me, then forget it....
Michael J. Sabal
m_sabal at yahoo.com
2. Re: Program overlays
I think the program overlay feature requested by Mike Sabal would be a great
feature to add to Euphoria.
Ken Rhodes
On Fri, 26 Jan 2001 09:30:24 -0500, Euphoria Programming for MS-DOS wrote:
> I'm at a point right now where a certain feature of Euphoria could be
very useful if it existed.
>
> Right now, if I want to run a different Euphoria program from within my
Euphoria program, I need to use system_exec("exw..... This requires a
second interpreter to be opened, with a separate shell, separate console,
etc. And if I want to pass full control over to the second program, I
can't. I have to add an abort(1) statement after this line to release the
current program. This all works as far as it goes, but it's not very
elegant.
>
> What I would like to see (I think it's been mentioned before) is
something like the following:
>
> run_euphoria("Myprog2.ex","param1 param2 param3")
>
> The interpreter would, upon processing this line, run the same cleanup
routine internally that abort() uses, but instead of terminating the
interpreter, re-initialize it with the new program and command-line options
(second parameter in the routine call).
>
> I'd love to see a call_euphoria(...) routine where control returns to the
original calling program upon termination of the called program, but I
imagine that would be more complex and too hard to maintain. I'd be happy
with just the first one.
>
> If Rob has any religious objections to a run_euphoria statement, I
suppose I could continue to kludge along unelegantly . I'd also like to
get some feedback from others whether or not they would find this kind of
functionality useful. If it's just me, then forget it....
>
> Michael J. Sabal
> m_sabal at yahoo.com
_______________________________________________________
Send a cool gift with your E-Card
http://www.bluemountain.com/giftcenter/
3. Re: Program overlays
On 26 Jan 2001, at 9:30, Sabal Mike wrote:
> I'm at a point right now where a certain feature of Euphoria could be very
> useful if it existed.
>
> Right now, if I want to run a different Euphoria program from within my
> Euphoria program, I need to use system_exec("exw..... This requires a second
> interpreter to be opened, with a separate shell, separate console, etc. And
> if I want to pass full control over to the second program, I can't. I have to
> add an abort(1) statement after this line to release the current program.
> This all works as far as it goes, but it's not very elegant.
>
> What I would like to see (I think it's been mentioned before) is something
> like the following:
>
> run_euphoria("Myprog2.ex","param1 param2 param3")
>
> The interpreter would, upon processing this line, run the same cleanup routine
> internally that abort() uses, but instead of terminating the interpreter,
> re-initialize it with the new program and command-line options (second
> parameter in the routine call).
>
> I'd love to see a call_euphoria(...) routine where control returns to the
> original calling program upon termination of the called program, but I imagine
> that would be more complex and too hard to maintain. I'd be happy with just
> the first one.
>
> If Rob has any religious objections to a run_euphoria statement, I suppose I
> could continue to kludge along unelegantly . I'd also like to get some
> feedback from others whether or not they would find this kind of functionality
> useful. If it's just me, then forget it....
I'd love this, if it could have access to the global vars in the program that
called it!
Kat
4. Re: Program overlays
Hi,
I know I have a habit (good? bad? indifferent?) or reading my email in
chronological order (received), and replying to a new topic before reading the
comments of those who have preceded me. That noted, ...
When I first encountered 42 flavors of BASIC, this was called "chaining," and
was a very common way of doing relatively large and complex tasks in the very
small amounts of memory (< 64K) that were typically available on microcomputers
at the time (1982ish). It's not a bad idea, although the original motivation -
limited memory - hopefully isn't a problem any more.
George
--
On Fri, 26 Jan 2001 09:30:24
Sabal Mike wrote:
>I'm at a point right now where a certain feature of Euphoria could be very
>useful if it existed.
>
>Right now, if I want to run a different Euphoria program from within my
>Euphoria program, I need to use system_exec("exw..... This requires a second
>interpreter to be opened, with a separate shell, separate console, etc. And if I
>want to pass full control over to the second program, I can't. I have to add an
>abort(1) statement after this line to release the current program. This all
>works as far as it goes, but it's not very elegant.
>
>What I would like to see (I think it's been mentioned before) is something like
>the following:
>
>run_euphoria("Myprog2.ex","param1 param2 param3")
>
>The interpreter would, upon processing this line, run the same cleanup routine
>internally that abort() uses, but instead of terminating the interpreter,
>re-initialize it with the new program and command-line options (second parameter
>in the routine call).
>
>I'd love to see a call_euphoria(...) routine where control returns to the
>original calling program upon termination of the called program, but I imagine
>that would be more complex and too hard to maintain. I'd be happy with just the
>first one.
>
>If Rob has any religious objections to a run_euphoria statement, I suppose I
>could continue to kludge along unelegantly . I'd also like to get some
>feedback from others whether or not they would find this kind of functionality
>useful. If it's just me, then forget it....
>
>Michael J. Sabal
>m_sabal at yahoo.com
>
Get your small business started at Lycos Small Business at
http://www.lycos.com/business/mail.html
