[asdf-devel] Tests completed

[Stelian Ionescu]

On Mon, 2014-01-13 at 10:05 -0600, Robert P. Goldman wrote:
> Faré wrote:
> >> I need to look into a means to identify these problematic cases.  Ugh.
> >> > MOP not standardized.  Ugh ugh ugh ugh.  I'll see if I can pilfer code
> >> > from Closer-MOP to render ENSURE-CLASS accessible.
> >> >
> >> > Is this the moral of this story: code that wishes to be backwards
> >> > compatible and portable can NEVER change the class hierarchy above an
> >> > API-visible class, because there is no *portable* way to detect when
> >> > someone's code will be affected.
> >> >
> > What if the previous hierarchy was plain buggy?
> 
> Then going forward we have to introduce a NEW class to replace the old
> class.

I hope you're only referring to new changes, not the ones that already
happened.

-- 
Stelian Ionescu a.k.a. fe[nl]ix
Quidquid latine dictum sit, altum videtur.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <https://mailman.common-lisp.net/pipermail/asdf-devel/attachments/20140113/786b1667/attachment.sig>