This is the mail archive of the
guile@cygnus.com
mailing list for the Guile project.
Re: mod_guile design problems
- To: Eric Moore <moore@lovecraft.chem.cmu.edu>
- Subject: Re: mod_guile design problems
- From: forcer <forcer@mindless.com>
- Date: 29 Jun 1999 22:02:27 +0200
- Cc: guile@cygnus.com
- References: <19990629153908.DA80CD3D9@lovecraft.chem.cmu.edu>
Eric Moore <moore@lovecraft.chem.cmu.edu> writes:
> > The only solution i see so far is to make a copy of the
> > request_rec structure and pass the copy to the Scheme code. When
> > it returns, i have to copy the values back, and free the copied
> > request_rec using the normal smob guides.
>
> Or you could make a smob wrapper for the pointer that checks to see if the
> pointer is valid, and then on return, set something that makes it invalid.
> (possibly even just setting the accessor function to one that throws an error.)
How do i check for a point to be "valid"?
I don't think that installing a signal handler that catches
SIGSEGV and longjmp's back is a "nice" idea :]
-forcer
--
((email . "forcer@mindless.com") (www . "http://forcix.cx/")
(irc . "forcer@#StarWars (IRCnet)") (gpg . "/other/forcer.gpg"))