This is the mail archive of the
mailing list for the Guile project.
Re: mod_guile design problems
Maciej Stachowiak <firstname.lastname@example.org> writes:
> Greg Badros wrote:
> > forcer <email@example.com> writes:
> > > Hmm.
> > > How about a "Shared Memory Environment" guile environment type
> > This would be super cool for writing Scwm modules, too-- I'd been
> > dreaming about this for a while, but it seems pretty hard, but the
> > payoff is great: modules could still be written in Scheme, still have
> > access to Scwm's data structures, but execute asynchronously in a
> > pre-emptively scheduled second process (a bit nicer than the cooperative
> > threads that Guile already has) that can crash and burn without killing
> > the window manager.
Having the whole SCWM top level environment in shared memory
would be overkill, imho. But communicating over this could be
> It seems to me that this model is not much better than pre-emptive OS-level
> threads, but much more complex to implement*. A process that can scribble
> into the Guile memory space can definitely screw it over pretty bad,
> whether it is in the same process or not.
Only if you share all environments.
My idea was to have one environment type that uses shared memory,
as a sort-of Scheme abstraction for shared memory. Would be nice
nontheless, for this purpose.
((email . "firstname.lastname@example.org") (www . "http://forcix.cx/")
(irc . "forcer@#StarWars (IRCnet)") (gpg . "/other/forcer.gpg"))