Thanks for your contribution Jan. It is interesting how in "CompatibilitySmalltalkX class>>initialize" you deal with missing classes by inserting what are essentially alias into the Smalltalk dictionary. So, I'm happy I learnt something new today.
Just curious though why both the class-side and instance-side #initialize methods set the same alias, but different ways. Also curious why "ClassDescription>>isClass" is blank. It would seem to need a boolean return value. cheers -ben On Fri, Sep 18, 2015 at 10:05 PM, Jan Vrany <[email protected]> wrote: > Thanks, Ben. Stuff copied. > > Cheers, Jan > > > On Fri, 2015-09-18 at 21:54 +0800, Ben Coman wrote: >> Jan, Thanks for your contribution. Actually I hadn't uploaded >> anything >> yet since I was waiting on more votes on renaming, but to push ahead >> I >> settled on SmalltalkCompatibility [1], since I think the repo can >> serve a wider purpose than just ANSI. >> >> I added you to the PharoExtras team. Hopefully that works. >> >> [1] http://smalltalkhub.com/#!/~PharoExtras/SmalltalkCompatibility >> >> cheers -ben >> >> On Fri, Sep 18, 2015 at 7:10 PM, Jan Vrany <[email protected]> >> wrote: >> > >> > > > I would rename it to SmalltalkCompatibility to >> > > > ANSICompatibility >> > > > because "Compatibility" is a too general term and could mean >> > > > backward compatibility >> > > > of Pharo versions or compatibility to other languages as well. >> > > >> > > That was me :) I was thinking more broadly that over time the >> > > "repository" might hold different packages Compatibility-ANSI, >> > > Compatibility-VW, Compatibility-Dolphin. But maybe that is >> > > overreaching and its better to be more focussed. Let me know what >> > > you >> > > think on this and restate what you think the repository name >> > > should >> > > be. >> > >> > Ben, could you please give me a commit access? I intend to >> > move Compatibility-SmalltalkX and Compatibility-ANSI (which >> > I created and "maintain" for my own need). Maybe some others >> > may find them useful or maybe even contribute. >> > >> > Cheers, Jan >> > >> > > >> > > > Also see http://wiki.squeak.org/squeak/2384 and >> > > > http://map.squeak.org/package/d7011055-4446-4b8e-b6da-e7e32d338 >> > > > 9ec >> > > > which could be a start. >> > > >> > > I saw those, but they interact with existing classes, so I >> > > thought it >> > > easier to kickstart by loading in the tests first, which are all >> > > new >> > > classes. I only created the repository since the tests were >> > > *hard* >> > > to >> > > find eventually at >> > > http://www.spacmunke.org/svn/jst/trunk/src/test/ansi/ansi-compati >> > > bili >> > > ty/ >> > > So I thought it would be good make them more accessible as a >> > > Monticello Package. >> > > >> > > cheers -ben >> > > >> > > P.S. I don't quite follow "to SmalltalkCompatibility to >> > > ANSICompatibility" >> > > do you mean "to SmalltalkCompatibility or ANSICompatibility" ? >> > > >> > > > >> > > > > Gesendet: Dienstag, 08. September 2015 um 22:53 Uhr >> > > > > Von: stepharo <[email protected]> >> > > > > An: "Pharo Development List" <[email protected]> >> > > > > Betreff: Re: [Pharo-dev] ANSICompatibility package >> > > > > >> > > > > We should have a SmalltalkCompatibility (not Ansi per se) >> > > > > package >> > > > > were we can add some methods to help migration. >> > > > > >> > > > > Stef >> > > > > >> > > > > >> > > > > Le 8/9/15 06:04, Ben Coman a écrit : >> > > > > > On Tue, Sep 8, 2015 at 9:21 AM, Jan Vrany < >> > > > > > [email protected]> wrote: >> > > > > > > Hi, >> > > > > > > >> > > > > > > is there actually such a thing like ANSICompatibility >> > > > > > > package? >> > > > > > > (it has been mentioned here lately, but I cannot find it) >> > > > > > > >> > > > > > > Thanks, Jan >> > > > > > > >> > > > > > I made it up for the purpose of discussion to see what >> > > > > > interest >> > > > > > it generated. >> > > > > > Should we start one ? >> > > > > > cheers -ben >> > > > > > >> > > > > > >> > > > > >> > > > > >> > > > > >> > > > >> > > >> > > >> > >> >> >
