[Openmcl-devel] trunk instability

Gary Byers gb at clozure.com
Sat Apr 4 11:48:38 PDT 2009

I checked some changes into the trunk early this morning that were
intended to make it easier to detect certain types of memory acccess
exceptions and report them as lisp errors (currently, some types of
invalid memory accesses are reported as lisp errors and others
aren't.)  It's entirely possible that those changes broke something
somewhere (and may not even compile on all platforms), so people
using the trunk might be well-advised not to update from it until
this is straightened out.  (That's probably going to be "hours" or
maybe "a day or two"; it shouldn't be much longer than that.)

More information about the Openmcl-devel mailing list