September 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Interesting Date/Time Thread on Squeak Dev

by Sean P. DeNigris

From http://forum.world.st/Next-version-of-Date-DateAndTime-and-Duration-API-upd… : Now in the InBox: KernelTests-cbc.278.mcz Kernel-cbc.871.mcz The tests add in test for expected Duration addition and subtraction from each other, including the new GenericMonth and GenericYear, and the very new GenericDuration. It also adds a few more tests for LeapYear tests with adding years to them. The test are still based on what it currently does, with the exceptions listed previously (I haven't really changed any to expect failures, as has been suggested - that will come shortly. For now, I want to try to cause little to no changes o expected behavior first - just new behavior for now). Kernel adds the GenericDuration, and handles adding and subtracting GenericMonth, GenericYear, and GenericDurations togeher in a rational way. This involves turning + and - in Durations into a double-dispatch so that it will work. There are no comments yet in these classes - they will be there before the weekend is over at the latest. Any comments are more than welcome. -cbc ----- Cheers, Sean -- View this message in context: http://forum.world.st/Interesting-Date-Time-Thread-on-Squeak-Dev-tp4778652p… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 19, 2014

Re: [Pharo-dev] How production ready is Pharo on SQLServer?

by Sean P. DeNigris

Tudor Girba-2 wrote > package: 'ConfigurationOfOpenDBXDriver'; > load. > #ConfigurationOfOpenDBXDriver asClass loadBleedingEdge. configurationOf: 'OpenDBXDriver'; loadVersion: #bleedingEdge. :) ----- Cheers, Sean -- View this message in context: http://forum.world.st/How-production-ready-is-Pharo-on-SQLServer-tp4777508p… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 19, 2014

Re: [Pharo-dev] How production ready is Pharo on SQLServer?

by Sebastian Sastre

yes if things where in markdown friendly wiki and git you'll see a pull request in half a second I'll think of something but returning to the dll issue, you mention you endd up using odbc and I see there are two backends to choose from. The odbc and the mssql, so, i'm getting this right? If I use odbc that dll is not needed? Any reason not to use odbc? from iPad > On 19/09/2014, at 08:05, "Torsten Bergmann" <astares(a)gmx.de> wrote: > > Hi Sebastian, > > The DLL's have to be where Pharo VM is or in the subfolder where the other DBX libs are. If in doubt put > it (temporarily) into C:/Windows/System32 as they will be found always then. No need to restart the OS but > you should reopen Pharo VM with image. > > You can find the missing DLL here: http://web.archiveorange.com/archive/v/a1gO5ZoJReyXr6T4n5m7 > Fortunately I bookmarked this one after going through the same hazzle. > You have to download "libsybdb-5.xxx" and rename to "libsybdb-5.dll". > > I went through all this pain in the past - very time wasting and not what I would call user friendly. > It is really a pity that no one is able to care about setting up a CI to build all the necessary > stuff ... > > In the end I used ODBC package as it is easy to load from the config browser and one only has > to setup an ODBC name. > > Hope this helps in your OpenDBX adventure... > > When successfull maybe you could put a tutorial and all the necessary binaries on a webpage/github/... afterwards. > Dont know how long the archive remembers the thread with the missing DLL. > > Thx > T. > > > Gesendet: Freitag, 19. September 2014 um 12:46 Uhr > Von: "Sebastian Sastre" <sebastian(a)flowingconcept.com> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Betreff: Re: [Pharo-dev] How production ready is Pharo on SQLServer? > > Thank you tudor that one loads. > > Answering a question about documentation mentions: > > Gofer it > smalltalkhubUser: 'DBXTalk' project: 'Configurations'; > configurationOf 'OpenDBXDriver'; loadStable. > > > > Which is consistent with the next step about the connectionSettings preparing to run the tests. > > > What I've experienced is that you need to > 1. copy all .dll's to the pharo dir > 2. set that in the windows path (reboot/relogon required) > 3. try connecting > > Minor issue: The tests assumes that you have a postgres backend so it will complain about you not having it installed (unless you do) > > Changing th ecode to use MSSQL leads to the apparently known issue of Windows complaining about > libsybdb-5.dll > > > More info here: > http://lists.squeakfoundation.org/pipermail/squeakdbx/2011-March/000337.html > > > As soon as you evaluate connect, you see that problem > > | conn connectionSettings | > connectionSettings := (DBXConnectionSettings > host: 'localhost' > port: '1433' > database: 'dbxtest' > userName: 'sa' > userPassword: '123'). > conn := DBXConnection platform: DBXMSSQLBackend new settings: connectionSettings. > conn connect. > conn open. > > > I have to continue later but I don't have clear yet where or who is suposed to install libsybdb-5.dll > > any help appreciated > > and thanks for the helpful tips in your replies > > seb > o/ > > ------------------------------------------------------------ > > De: "Tudor Girba" <tudor(a)tudorgirba.com> > Para: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Enviadas: Sexta-feira, 19 de setembro de 2014 4:35:31 > Assunto: Re: [Pharo-dev] How production ready is Pharo on SQLServer? > > Here is how to load and install DBXTalk in Pharo 3.0: > > > Gofer new > smalltalkhubUser: 'DBXTalk' project: 'DBXTalkDriver'; > package: 'ConfigurationOfOpenDBXDriver'; > load. > #ConfigurationOfOpenDBXDriver asClass loadBleedingEdge. > #NBPharoOpenDBX asClass installAsCurrent. > > > Cheers, > Doru > > > On Fri, Sep 19, 2014 at 8:45 AM, Esteban Lorenzano <estebanlm@gmail.com[estebanlm@gmail.com]> wrote:yeahâ¦ I told you that dbxtalk site information is outdated (and never find the time to update) > > you need to look here: > > http://smalltalkhub.com/#!/~DBXTalk/Configurations[http://smalltalkhub.com/… > > (or in the configuration browser) > > cheers, > Esteban > >> On 19 Sep 2014, at 08:00, Stephan Eggermont <stephan@stack.nl[stephan@stack.nl]> wrote: >> >> Sebastian, that doesn't look like the correct one >> DBXTalk is on smalltalkhub >> >> https://ci.inria.fr/dbxtalk/[https://ci.inria.fr/dbxtalk/] >> >> Stephan > > > -- > www.tudorgirba.com[http://www.tudorgirba.com] > > "Every thing has its own flow" > >

Sept. 19, 2014

Re: [Pharo-dev] How production ready is Pharo on SQLServer?

by Torsten Bergmann

Hi Sebastian, The DLL's have to be where Pharo VM is or in the subfolder where the other DBX libs are. If in doubt put it (temporarily) into C:/Windows/System32 as they will be found always then.Â No need to restart the OS but you should reopen Pharo VM with image. Â You can find the missing DLL here: Â http://web.archiveorange.com/archive/v/a1gO5ZoJReyXr6T4n5m7 Fortunately I bookmarked this one after going through the same hazzle. You have to download "libsybdb-5.xxx"Â and rename to "libsybdb-5.dll".Â Â I went through all thisÂ pain in the past - very time wasting and not what I would call user friendly. It is really a pity that no one is able to care about setting up a CI to build all the necessary stuff ... In the end I used ODBC package as it is easy to load from the config browser and one only has to setup an ODBC name. Hope this helps in your OpenDBX adventure... When successfull maybe you could put a tutorial and all the necessary binaries on a webpage/github/... afterwards. Dont know how long the archive remembers the thread with the missing DLL. Thx T. Â Gesendet:Â Freitag, 19. September 2014 um 12:46 Uhr Von:Â "Sebastian Sastre" <sebastian(a)flowingconcept.com> An:Â "Pharo Development List" <pharo-dev(a)lists.pharo.org> Betreff:Â Re: [Pharo-dev] How production ready is Pharo on SQLServer? Thank you tudor that one loads. Â Answering a question about documentation mentions: Â Gofer it smalltalkhubUser: 'DBXTalk' project: 'Configurations'; configurationOf 'OpenDBXDriver'; loadStable. Â Which is consistent with the next step about the connectionSettings preparing to run the tests. Â Â What I've experienced is that you need to 1. copy all .dll's to the pharo dir 2. set that in the windows path (reboot/relogon required) 3. try connecting Â Minor issue: The tests assumes that you have a postgres backend so it will complain about you not having it installed (unless you do) Â Changing th ecode to use MSSQL leads to the apparently known issue of Windows complaining aboutÂ libsybdb-5.dll Â More info here: http://lists.squeakfoundation.org/pipermail/squeakdbx/2011-March/000337.html Â Â As soon as you evaluate connect, you see that problemÂ Â | conn connectionSettings | connectionSettings := (DBXConnectionSettings host: 'localhost' port: '1433' database: 'dbxtest' userName: 'sa' userPassword: '123'). conn := DBXConnection platform: DBXMSSQLBackend new settings: connectionSettings. conn connect. conn open. Â I have to continue later but I don't have clear yet where or who is suposed to installÂ libsybdb-5.dll Â any help appreciated Â and thanks for the helpful tips in your replies Â seb o/ Â ------------------------------------------------------------ De: "Tudor Girba" <tudor(a)tudorgirba.com> Para: "Pharo Development List" <pharo-dev(a)lists.pharo.org> Enviadas: Sexta-feira, 19 de setembro de 2014 4:35:31 Assunto: Re: [Pharo-dev] How production ready is Pharo on SQLServer? Â Here is how to load and install DBXTalk in Pharo 3.0: Â Gofer new Â Â Â smalltalkhubUser: 'DBXTalk' project: 'DBXTalkDriver'; Â Â Â package: 'ConfigurationOfOpenDBXDriver'; Â Â Â load. Â Â Â #ConfigurationOfOpenDBXDriver asClass loadBleedingEdge. Â #NBPharoOpenDBX asClass installAsCurrent. Â Â Cheers, Doru Â Â On Fri, Sep 19, 2014 at 8:45 AM, Esteban Lorenzano <estebanlm@gmail.com[estebanlm@gmail.com]> wrote:yeahâ¦ I told you that dbxtalk site information is outdated (and never find the time to update) you need to look here: http://smalltalkhub.com/#!/~DBXTalk/Configurations[http://smalltalkhub.com/… (or in the configuration browser) cheers, Esteban On 19 Sep 2014, at 08:00, Stephan Eggermont <stephan@stack.nl[stephan@stack.nl]> wrote: > Sebastian, that doesn't look like the correct one > DBXTalk is on smalltalkhub > > https://ci.inria.fr/dbxtalk/[https://ci.inria.fr/dbxtalk/] > > Stephan > Â Â Â -- www.tudorgirba.com[http://www.tudorgirba.com] Â "Every thing has its own flow" Â

Sept. 19, 2014

Re: [Pharo-dev] How production ready is Pharo on SQLServer?

by Sebastian Sastre

Thank you tudor that one loads. Answering a question about documentation mentions: Gofer it smalltalkhubUser: 'DBXTalk' project: 'Configurations' ; configurationOf 'OpenDBXDriver'; loadStable. Which is consistent with the next step about the connectionSettings preparing to run the tests. What I've experienced is that you need to 1. copy all .dll's to the pharo dir 2. set that in the windows path (reboot/relogon required) 3. try connecting Minor issue: The tests assumes that you have a postgres backend so it will complain about you not having it installed (unless you do) Changing th ecode to use MSSQL leads to the apparently known issue of Windows complaining about libsybdb-5.dll More info here: http://lists.squeakfoundation.org/pipermail/squeakdbx/2011-March/000337.html As soon as you evaluate connect, you see that problem | conn connectionSettings | connectionSettings := (DBXConnectionSettings host: 'localhost' port: '1433' database: 'dbxtest' userName: 'sa' userPassword: '123'). conn := DBXConnection platform: DBXMSSQLBackend new settings: connectionSettings. conn connect. conn open. I have to continue later but I don't have clear yet where or who is suposed to install libsybdb-5.dll any help appreciated and thanks for the helpful tips in your replies seb o/ ----- Mensagem original ----- De: "Tudor Girba" <tudor(a)tudorgirba.com> Para: "Pharo Development List" <pharo-dev(a)lists.pharo.org> Enviadas: Sexta-feira, 19 de setembro de 2014 4:35:31 Assunto: Re: [Pharo-dev] How production ready is Pharo on SQLServer? Here is how to load and install DBXTalk in Pharo 3.0: Gofer new smalltalkhubUser: 'DBXTalk' project: 'DBXTalkDriver'; package: 'ConfigurationOfOpenDBXDriver'; load. #ConfigurationOfOpenDBXDriver asClass loadBleedingEdge. #NBPharoOpenDBX asClass installAsCurrent. Cheers, Doru On Fri, Sep 19, 2014 at 8:45 AM, Esteban Lorenzano < estebanlm(a)gmail.com > wrote: yeahâ¦ I told you that dbxtalk site information is outdated (and never find the time to update) you need to look here: http://smalltalkhub.com/#!/~DBXTalk/Configurations (or in the configuration browser) cheers, Esteban On 19 Sep 2014, at 08:00, Stephan Eggermont < stephan(a)stack.nl > wrote: > Sebastian, that doesn't look like the correct one > DBXTalk is on smalltalkhub > > https://ci.inria.fr/dbxtalk/ > > Stephan > -- www.tudorgirba.com "Every thing has its own flow"

Sept. 19, 2014

Re: [Pharo-dev] Filetree and Git and Github

by phil＠highoctane.be

On Fri, Sep 19, 2014 at 11:32 AM, kilon alios <kilon.alios(a)gmail.com> wrote: > I have been told that there are some problem with gitfiletree that make it > not recommended for public consumption and recommendation to newcomers. > > I have been using not gitfiletree but filetree alone for the past week for > my project Ephestos, because I am ok commiting to git via terminal/ > > https://github.com/kilon/phEphestos > > I have to congratulate people behind filetree it has been a smooth ride so > far.I had no problems with it at all and I am using git in terminal for > doing all the git commits and push etc. > > filetree also has been very succesful at some major refactoring I have > done to Ephestos, I had to change the name of an entire class and I had to > change methods to other classes . Filetree did an excellent job not just > with the export to st file but actually git was able to see which files > were deleted and which were renamed. > > That meant I did not have to do any git rm . > > However I do need to git add every time I add a new method or filetree > creates a new file. Usually that is not a problem because I can see what > files are not tracked by git with git status and copy paste their paths to > git add. > > So I will say overall my commits have been a process of saving in > monticello , git add, git commit and git push which exactly the same > process I have used for when I was and still coding in python. > > So thank you for this tool , I got fed up with the slow downs of > Smalltalkhub and all its problems and it feels great to be back at using > github :) > I'd agree to that thing. Took me a while but now the Git based workflow just feels better. Also useful is storing snippets as gists. Git has won, let's embrace that. This doesn't mean that STH is not useful as a project repository. MCZs are still the main artifact. > I will keep testing for a couple a months and then completely move to > github . The only thing I noticed is that sometimes monticello slows down > but that may well be a problem with Pharo 4. >

Sept. 19, 2014

[pharo-project/pharo-core] a53477: 40234

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: a5347722741a52b59c77091c4af73d0799f8ed57 https://github.com/pharo-project/pharo-core/commit/a5347722741a52b59c77091c… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-09-19 (Fri, 19 Sep 2014) Changed paths: A Deprecated40.package/extension/Locale/class/addLocalChangedListener_.st A Deprecated40.package/extension/Locale/class/isoLocale_.st A Deprecated40.package/extension/Locale/class/localeChanged.st A Deprecated40.package/extension/Locale/class/localeChangedListeners.st A Deprecated40.package/extension/LocaleID/class/previous.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script234.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40234.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A System-Localization-Tests.package/ISOLanguageDefinitionTest.class/README.md A System-Localization-Tests.package/ISOLanguageDefinitionTest.class/definition.st A System-Localization-Tests.package/ISOLanguageDefinitionTest.class/instance/tests/testISO2LanguageDefinition.st A System-Localization-Tests.package/ISOLanguageDefinitionTest.class/instance/tests/testISO3LanguageDefinition.st A System-Localization-Tests.package/LocaleAnnouncementTests.class/README.md A System-Localization-Tests.package/LocaleAnnouncementTests.class/definition.st A System-Localization-Tests.package/LocaleAnnouncementTests.class/instance/events/localeWasChanged_.st A System-Localization-Tests.package/LocaleAnnouncementTests.class/instance/private accessing/frenchLocale.st A System-Localization-Tests.package/LocaleAnnouncementTests.class/instance/running/setUp.st A System-Localization-Tests.package/LocaleAnnouncementTests.class/instance/running/tearDown.st A System-Localization-Tests.package/LocaleAnnouncementTests.class/instance/tests/testLocaleChangeAnnouncement.st A System-Localization-Tests.package/LocaleChangedTest.class/README.md A System-Localization-Tests.package/LocaleChangedTest.class/definition.st A System-Localization-Tests.package/LocaleChangedTest.class/instance/private accessing/englishLocale.st A System-Localization-Tests.package/LocaleChangedTest.class/instance/private accessing/germanLocale.st A System-Localization-Tests.package/LocaleChangedTest.class/instance/tests/testInstanceCreation.st A System-Localization-Tests.package/LocaleIDTest.class/README.md A System-Localization-Tests.package/LocaleIDTest.class/definition.st A System-Localization-Tests.package/LocaleIDTest.class/instance/tests - test data/frenchLocaleID.st A System-Localization-Tests.package/LocaleIDTest.class/instance/tests - test data/germanLocaleID.st A System-Localization-Tests.package/LocaleIDTest.class/instance/tests/testComparision.st A System-Localization-Tests.package/LocaleIDTest.class/instance/tests/testCurrent.st A System-Localization-Tests.package/LocaleIDTest.class/instance/tests/testFromISOString.st A System-Localization-Tests.package/LocaleIDTest.class/instance/tests/testFromSingleISOString.st A System-Localization-Tests.package/LocaleIDTest.class/instance/tests/testHashing.st A System-Localization-Tests.package/LocaleIDTest.class/instance/tests/testInstanceCreationWithISOLanguage.st A System-Localization-Tests.package/LocaleIDTest.class/instance/tests/testInstanceCreationWithISOLanguageAndCountry.st A System-Localization-Tests.package/LocaleIDTest.class/instance/tests/testPosixNameConversion.st A System-Localization-Tests.package/LocaleIDTest.class/instance/tests/testPrintString.st A System-Localization-Tests.package/LocaleTest.class/README.md A System-Localization-Tests.package/LocaleTest.class/definition.st A System-Localization-Tests.package/LocaleTest.class/instance/tests/testAccessLocaleID.st A System-Localization-Tests.package/LocaleTest.class/instance/tests/testCurrent.st A System-Localization-Tests.package/NaturalLanguageTranslatorTest.class/README.md A System-Localization-Tests.package/NaturalLanguageTranslatorTest.class/definition.st A System-Localization-Tests.package/NaturalLanguageTranslatorTest.class/instance/running/setUp.st A System-Localization-Tests.package/NaturalLanguageTranslatorTest.class/instance/running/tearDown.st A System-Localization-Tests.package/NaturalLanguageTranslatorTest.class/instance/tests/testRegisterCustomTranslator.st A System-Localization-Tests.package/NaturalLanguageTranslatorTest.class/instance/tests/testTranslatePureString.st A System-Localization-Tests.package/RegisterableTranslatorMock.class/README.md A System-Localization-Tests.package/RegisterableTranslatorMock.class/definition.st A System-Localization-Tests.package/RegisterableTranslatorMock.class/instance/initialization/initialize.st A System-Localization-Tests.package/RegisterableTranslatorMock.class/instance/translate/translate_.st A System-Localization-Tests.package/RegisterableTranslatorMock.class/instance/translate/translate_toLocale_.st A System-Localization.package/ISOLanguageDefinition.class/class/private - ISO 2/iso2Countries.st A System-Localization.package/ISOLanguageDefinition.class/class/private - ISO 2/iso2LanguageTable.st A System-Localization.package/ISOLanguageDefinition.class/class/private - ISO 3/iso3Countries.st A System-Localization.package/ISOLanguageDefinition.class/class/private - ISO 3/iso3LanguageTable.st A System-Localization.package/ISOLanguageDefinition.class/class/private - ISO 3166/buildIso3166CodesTables.st A System-Localization.package/ISOLanguageDefinition.class/class/private - ISO 3166/initISO3LanguageTable.st A System-Localization.package/ISOLanguageDefinition.class/class/private - ISO 3166/iso3166Codes.st R System-Localization.package/ISOLanguageDefinition.class/class/private/buildIso3166CodesTables.st R System-Localization.package/ISOLanguageDefinition.class/class/private/initISO3LanguageTable.st R System-Localization.package/ISOLanguageDefinition.class/class/private/iso2Countries.st R System-Localization.package/ISOLanguageDefinition.class/class/private/iso2LanguageTable.st R System-Localization.package/ISOLanguageDefinition.class/class/private/iso3166Codes.st R System-Localization.package/ISOLanguageDefinition.class/class/private/iso3Countries.st R System-Localization.package/ISOLanguageDefinition.class/class/private/iso3LanguageTable.st M System-Localization.package/ISOLanguageDefinition.class/definition.st R System-Localization.package/Locale.class/class/accessing/isoLocale_.st M System-Localization.package/Locale.class/class/accessing/switchTo_.st A System-Localization.package/Locale.class/class/announcing/localeAnnouncer.st R System-Localization.package/Locale.class/class/notification/addLocalChangedListener_.st R System-Localization.package/Locale.class/class/notification/localeChanged.st R System-Localization.package/Locale.class/class/notification/localeChangedListeners.st M System-Localization.package/Locale.class/definition.st A System-Localization.package/LocaleChanged.class/README.md A System-Localization.package/LocaleChanged.class/class/instance creation/from_to_.st A System-Localization.package/LocaleChanged.class/definition.st A System-Localization.package/LocaleChanged.class/instance/accessing/newLocale.st A System-Localization.package/LocaleChanged.class/instance/accessing/newLocale_.st A System-Localization.package/LocaleChanged.class/instance/accessing/oldLocale.st A System-Localization.package/LocaleChanged.class/instance/accessing/oldLocale_.st R System-Localization.package/LocaleID.class/class/accessing/previous.st M System-Localization.package/LocaleID.class/definition.st M System-Localization.package/NaturalLanguageTranslator.class/README.md A System-Localization.package/NaturalLanguageTranslator.class/class/accessing/current.st A System-Localization.package/NaturalLanguageTranslator.class/class/accessing/current_.st M System-Localization.package/NaturalLanguageTranslator.class/class/cleanup/cleanUp.st M System-Localization.package/NaturalLanguageTranslator.class/class/translate/translate_.st M System-Localization.package/NaturalLanguageTranslator.class/class/translate/translate_toLocale_.st M System-Localization.package/NaturalLanguageTranslator.class/definition.st Log Message: ----------- 40234 14026 Cleanup System-Localization package and add tests https://pharo.fogbugz.com/f/cases/14026 http://files.pharo.org/image/40/40234.zip

Sept. 19, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40234 Home: https://github.com/pharo-project/pharo-core

Sept. 19, 2014

Re: [Pharo-dev] Versioner does not work on Pharo 4

by Christophe Demarey

Le 19 sept. 2014 Ã 11:21, kilon alios a Ã©crit : > Well to kepp you updated , because I did not bother replying to my own thread since none seemed to care or have the same issue as me. I was out of office last days ... > I tried on windows again same error as macos on a fresh image by the way. So I know it must not be me. On which image? I just tried on a fresh 3.0 image and it also works for me. > The only things I am doing with pharo is > > 1) use dark theme > > 2) use free type font Arial on windows and Monaco on macos > > 3) use filetree for working with a git directory. Maybe a side effect. Could you give me a script to help reproducing the problem? Maybe just your startup script. Does the problem appear the first time you open Versionner? Thanks, Christophe.

Sept. 19, 2014

Implementing lazy loading for expandable collections

by Max Leske

Iâve written an implementation of lazily initialized expandable collections (for OrderedCollection and subclasses only for now), inspired by Alexandreâs talk at ESUG (http://www.youtube.com/watch?v=x0YJ2dsZdKg&list=UUO-vBhaKVZf0al-ISMMPvRw) The implementation is pretty much straight forward but there are a couple of culprits I want to point out in case anybody else wants to do this: - my implementation requires an extra instance variable in OrderedCollection to store the requested size. This extra instance variable will break Monticello (and possibly other tools) because Monticello uses OrderedCollections to load code and the particular way it uses them makes it impossible to change the number of instance variables on OrderedCollection. Also, all .mcz files written after the change will not be loadable by images without the new instance variable (same reason). - the above means that you have to modify the code in the image manually and save a new âbase image" - read only messages should obviously not initialize the array. The âfirstIndexâ and âlastIndexâ variables are quite handy for that. I initialize those variables to 1 and 0 respectively which makes most things work already (e.g. #size, #isEmpty etc.). - when trying to implement the same for HashedCollection I couldnât. The image didnât just stop working, there was no output at all on the console, not even when using a debug VM. The problem seems to be MethodDictionary, at least thatâs the only subclass of Dictionary for which adding an instance variable doesnât work. Iâll share some memory monitoring as soon as I have something significant (only just rolled it out). Big thanks to Alex for his talk and the cool work he and his students did! Cheers, Max

Sept. 19, 2014