This is the mail archive of the guile@cygnus.com mailing list for the Guile project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: mod_guile design problems


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"))

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]