December 2018 - Pharo-users

Re: [Pharo-users] subpackages in P7

by Sean P. DeNigris

Peter Uhnak wrote > That's why MyPackage-Test is best kept separate, because when other > project > is loading your project, they don't need to load such package Just to give another angle, while everything said in this thread is true, I typically start with a monolithic package + sub tags and only split the package if forced to. I view premature splitting as similar to premature optimization. There is a cost of increased complication with dependencies and related management. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Dec. 1, 2018

Re: [Pharo-users] Unable to compile myself Pharo

by Pierce Ng

On Fri, Nov 30, 2018 at 07:15:22PM +0100, Alexandre Garreau wrote: > But I saw the bootstrap process involve redownloading a binary image > anywayâ¦ Iâd have just prefered to recompile it to be sure, as Iâm > usually more comfortable with this idea. Normally compiling a new > language is âthough longâ not that difficult. For Pharo (and relatives like Squeak and Cuis) there are two parts: VM and image. To build your own VM, follow the README's instructions for the OpenSmalltalk VM: https://github.com/OpenSmalltalk/opensmalltalk-vm As for building your own images, for now, I suggest to use the standard downloadable images. Pierce

Dec. 1, 2018

What is the actual way of managing code in Pharo

by Ichiseki

Hi there, I am trying the new Pharo 7 and a very elemental question arose. What I should use to manage my code? Monticello Metacello Iceberg It seems I am quite confused regarding the role of each of these tools. Documentation, I am afraid, does not apply to Pharo 7. The chapters covering Monticello and Metacello in Deep in to Pharo, are still relevant in Pharo 7? Please I need profound and detailed help on this. Thanks so much best Ichi -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Dec. 1, 2018