On 24 September 2013 17:06, Goubier Thierry <[email protected]> wrote:
> > > Le 24/09/2013 16:50, Igor Stasenko a écrit : > >> >> >> On 24 September 2013 15:31, Goubier Thierry <[email protected] >> <mailto:[email protected]**>> wrote: >> >> I'm managing to get MNUs in Pharo 3.0 in a quite fun way. >> >> I've compiled methods with nil as protocol... The result is kind of >> interesting. >> >> >> i think it is because nil is no longer valid protocol. sure thing it >> should not lead to dnu but to some more >> clear error message. >> > > Well, nil wasn't a protocol either in 2.0 but it was ignored :) > > > anyways, thanks for finding the bug >> > > I triggered it with > > aClass compile: 'test ^true' classified: nil notifying: nil > > :) > > There is also another behavior difference between 2.0 and 3.0: the > protocol #'as yet unclassified' disappear when empty in 2.0 and it stays, > even empty, in 2.0. > > Do you intend it that way? > I don't know the details, there was a lot of work done by Esteban refactoring this.. so i letting him to answer your question. > > Regards, > > > Thierry > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des Systèmes Temps Réel Embarqués > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 > > -- Best regards, Igor Stasenko.
