Re: call_back() etc

new topic     » goto parent     » topic index » view thread      » older message » newer message

Im almost entirely unfamiliar with win32/object oriented/dll stuff, but let
me see if I can try one more time:

What I've played with so far:

Run ProgA
    Code
    system_exec(ProgB)
    Code
end ProgA

What I really want to happen is for ProgA to be able to invoke Euphoria to
intrepret ProgB, and then use the functions ProgB has created.  Basically,
ProgA needs the ability to temporarily add Euphoria-intepreted code from an
external file on the fly:

Run ProgA
    ProgA code
    Run ProgB
        Register ProgB functions/procedures with ProgA
    ProgA code using ProgB functions/procedures
    end ProgB
        Unregister ProgB functions/procedures from ProgA
    ProgA code
end ProgA

It was suggested earlier that the new code could be added as includes to the
original code and then re-run.  However, I want the ability to add several
new scripts, and to drop them quickly, without significant interruption of
the program.

Okay, I'm still not quite sure what you're looking for... it sounds

> like you're trying to get one program to execute code that's in another
> program, WITHOUT putting that code in the first program at all (via an
> include, or directly.) Or are you wanting one program to tell another
> to execute a specific function?
>
> In the latter case, would it suit your needs if, instead of using the
> temp file to pass call_back() values (I'm not even sure you can use that
> with the DOS32 version of Euphoria), you passed actual function names?
> For example, instead of of doing:
>
>    id = routine_id ("f")
>    callback_val = call_back (id)
>
> and writing callback_val to the other temp file, would just writing "f"
> to the file accomplish what you want?
>
> Rod

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu