> > I still think, you should - if possible - check somehow if the > > programmer is inside an sdl-environment, it is not good that you can > > segfault a program with a library. It may happen (due to bugs or > > something like that), but it should not be the "default" behavior - > > however, this is your decision, and its just a design-issue. > > > > > > I might consider adding this check *only* in functions that create, load, > or convert a SURFACE, as I can't see these being called on a per-frame > basis.
This would be at least better than no checks at all. > But functions that blit, or read from, or fill, or create new RECTANGLE's > etc. will not perform this check. > > Justin, any thoughts? At least SBCL seems to allow to catch Memory-Faults. But I do not know if this is efficient enough. Another Idea would be to somehow redefine certain functions when entering and exiting an sdl-scope, that is, they cannot be called outside the scope - but this is - if it was possible and fast enough to use it - a lot of work, I think. Maybe you should just write it into the Documentation (at a Place where anyone can see it). MfG CSS _______________________________________________ application-builder mailing list application-builder@lispniks.com http://www.lispniks.com/mailman/listinfo/application-builder
