Re: EXCL 2.0 FASL FILE ORDERING BUG WITH PCL

[Gregor.pa@Xerox.COM]

The new version of PCL deals with this problem automatically.

Unless you are describing a different problem, the problems isn't really
that ExCL (or any of the other lisps which have this problem) reorder
forms in the FASL file, its that they allow themselves to group forms.
This can cause a load-time-eval which follows a defclass to actually be
evaluated before a defclass.  This happens when you use
call-next-method.   The canonical way to lose is:

(defclass foo () ())

(defmethod bar ((x foo)) (call-next-method))