Craig Latta schrieb:

I'm sorry if I'm annoying ;-)

>      Every version of every module, author, class, and metaclass has a
> UUID. Methods are uniquely identified by a combination of a class or
> metaclass version and a selector. Names are never needed to transfer
> behavior between systems.

This was something when I first - with my modes knowledge - tried to do
some bytecode serialization within squeak. I ended up in serializing
half of the image half of the times, trying to walk down the
dependencies between classes, behavious, constants and pool dictionaries.

Is there a methology to identify identical behaviours/ objects even if
identified by different UUIDs? Or is there a another approach like
creating the "UUID'd ancestor" which will provide the unique base and
which will be 'patched' (for the very base kernel) with commonly agreed/
shared UUIDs?

I am interested to understand the implications and I hope I am asking
the question that a 'reasonable Naiad newbie' will ask himself when he
comes across this list only to find these archived postings ;-)

>      You'll need to have signed and returned the Squeak project
> contributor's agreement to have your code included in the official
> Squeak releases, and the agreement is MIT-style, yes.

I think (correct me if I'm wrong) that this precondition is not
advertised on squeak.org. I would have just provided DNUs and fixes to
squeak-general if celest would have worked for me ;-)

Kind regards,
         Markus

-- 
Official PITA