OpenEuphoria

Re: Interprocess Communication...

• Posted by Patrick Barnes <mrtrick at gmail.com> Nov 10, 2004
• 478 views

On Wed, 10 Nov 2004 16:06:08 -0600, Kat <gertie at visionsix.com> wrote:
> > I'm not using IPC for the purposes of threads! I have a main program
> > that has expandable 'modules'. Each module is a Euphoria program that
> > conforms to the module framework (includes the framework library,
> > contains certain procedures, etc). Similarly to win32lib, the last
> > statement of the program cedes control to the framework library.
> >
> > That way, new modules can be added while the main program is still
> > running, and if a nasty error (as not all modules will be written by
> > me) occurs, the main program does not crash.
> >
> > It could be single-threaded, I don't care! My main question is, what
> > happens if something goes wrong in a module program? I know there are
> > a few projects that use IPC - MEditor for one...
> 
> Depening on how you set ipc up, you can have the main process dependant
> on the spawned processes or not. It's the best thing since slice bread (no
> joking). In the place of threads, and even if we do get threads, the ipc may
> be
> better, since it allows (mandates) separate everything except what the coder
> wishes to share.

Yes, it would be very nice if a form of IPC was integrated with
Euphoria. Apart from the other advantages, we could even make the
Euphoria equivalent of DLLs!

> If you want to use Eu code on separate operating systems in the same way
> as ipc, check out the socks code in the archives. I linked mirc and eu on
> win95 to a vb app on winxp, and php running on nix once, over the internet,
> altho you can do the same on a lan.

No, they are on the same computer. The reason they're separate
programs is because this is in regards to my preparing the second
contest, so I'm gonna be a little secretive about details. (This is
for the framework each competitor will use, not the actual goal of the
contest)

The main thing is - if a program crashes when one of its functions is
called remotely, does it crash the calling program, and can the
calling program detect that the other program crashed?

Looking at the internal code in IPC.ew, it uses the C function
"SendMessageA" to access the function in the other program (identified
using call_back()  )
-- 
MrTrick