Re: Interprocess Communication...
On Wed, 10 Nov 2004 13:01:45 -0600, Kat <gertie at visionsix.com> wrote:
> > I'm trying to use PatRat's IPC.ew library, and I have a few questions
> > about how it all works...
> > (Basically, it does some trickery with shared memory, call_backs, and
> > other low-level stuff)
>
> We should ban him from the list, tell him to go use a language that provides
> threads already, and then burn him at the stake. No one needs ipc, just like
> no one needs goto. He allows you to clutter up the machine with those other
> threads. It's not inately in Eu, and therefor it's BAD. Hang him! Same with
> all
> those people writing games by using winapi calls! They're DEMONS!
Uh, I most sincerely hope you're joking. (Suspected, given the GOTO
discussions earlier)
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...
--
MrTrick
|
Not Categorized, Please Help
|
|
