[gambit-list] What is the best strategy to ensure that non-FFI code can never cause sigsegv:s / bus errors?

Bradley Lucier lucier at math.purdue.edu
Wed Jul 9 10:30:29 EDT 2008

On Jul 9, 2008, at 10:15 AM, Mikael More wrote:

> ( I suppose for starters, it is not to override the default  
> (declare (safe)) declaration. What more? )

As far as I know, that should be it.  What I also find helpful is to  
use type-specific arithmetic operations (fx+, fx-, ... or fl+,  
fl-,...) when you expect the types of the arguments to be known;  
together with (declare (safe)), this will check your assumptions and  
tell you if you're wrong.


More information about the Gambit-list mailing list