May 2018 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Lazy vs eager initialization

by sergio ruiz

This makes sense.. in the the cases i am writing now, all objects will, by definition, have a bunch objects in the collection.. Thanks! On May 29, 2018 at 12:02:53 PM, Norbert Hartl (norbert(a)hartl.name) wrote: Lazy initialization is good if you only want to assign additional objects when needed. So if it would be a storage optimization you could make it in a way that only those who have pets get a collection assigned.Â ---- peace, sergio photographer, journalist, visionary Public Key:Â http://bit.ly/29z9fG0 #BitMessageÂ BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.codeandmusic.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

May 29, 2018

Re: [Pharo-users] Lazy vs eager initialization

by Norbert Hartl

> Am 29.05.2018 um 17:49 schrieb sergio ruiz <sergio.rrd(a)gmail.com>: > > If a model has a list of things.. such as a user that can/may have lots of pets, are there any real benefits to initializing the list of pets lazily? > > like: > > self pets := OrderedCollection new. > > vs. > > pets > pets ifNil: [self pets: OrderedCollection new] > ^ pets > Lazy initialization is good if you only want to assign additional objects when needed. So if it would be a storage optimization you could make it in a way that only those who have pets get a collection assigned. The downside is on the one hand that it raises concurrency problems because if two processes call #pets at the same time it could be that two collections are created and the two processes have each one of them and only one is stored in the pets holder. On the other hand lazy init makes you use the getter even inside the object (to assure the collection is created). I usually like to avoid having getters if not really needed but a lazy init style makes this a (bad) habit. So my advize would be that if you donât have a reason to do so make the initialization of this collection in the #initialize method and use the instVar accessin the methods of the pets holder. Try not to have a getter for the pets collection Norbert

May 29, 2018

Lazy vs eager initialization

by sergio ruiz

If a model has a list of things.. such as a user that can/may have lots of pets, are there any real benefits to initializing the list of pets lazily? like: self pets := OrderedCollection new. vs. pets Â pets ifNil: [self pets: OrderedCollection new] Â ^ pets thanks! ---- peace, sergio photographer, journalist, visionary Public Key:Â http://bit.ly/29z9fG0 #BitMessageÂ BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.codeandmusic.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

May 29, 2018

Re: [Pharo-users] Set Rounding mode for IEEE floating point operations

by Serge Stinckwich

On Tue, May 29, 2018 at 4:15 PM Steffen MÃ¤rcker <merkste(a)web.de> wrote: > Dear Serge, > > on the VM mailing list, Levente pointed out, that this could also be > related to some lib the VM uses (e.g., Freetype) that might change the > rounding mode. I'll dig into it and give your idea a try and come back > with the results. > > I think it would be nice to have in Pharo 7. But before I want to make > sure it a) works as expected and b) does not cause some nasty side effects. > > âYes in order to avoid any side effect, we can use what you propose before. An API like : Double roundToMinusInfWhile: [... code goes here ...]â âso we don't expose the rest of the system to these modifications. See you.â -- Serge Stinckwich UMI UMMISCO 209 (SU/IRD/UY1) "Programs must be written for people to read, and only incidentally for machines to execute."http://www.doesnotunderstand.org/

May 29, 2018

Re: [Pharo-users] Set Rounding mode for IEEE floating point operations

by Steffen MÃ¤rcker

Dear Serge, on the VM mailing list, Levente pointed out, that this could also be related to some lib the VM uses (e.g., Freetype) that might change the rounding mode. I'll dig into it and give your idea a try and come back with the results. I think it would be nice to have in Pharo 7. But before I want to make sure it a) works as expected and b) does not cause some nasty side effects. Bye, Steffen Am .05.2018, 12:26 Uhr, schrieb Serge Stinckwich <serge.stinckwich(a)gmail.com>: > On Thu, May 24, 2018 at 12:27 PM Steffen MÃ¤rcker <merkste(a)web.de> wrote: > >> Hi, >> >> now I've observed the same issue. It might be related to context >> switching, since introducing a delay has a similar effect. Consider: >> >> | FE_TONEAREST FE_DOWNWARD FE_UPWARD FE_TOWARDZERO | >> FE_TONEAREST := 16r0000. >> FE_DOWNWARD := 16r0400. >> FE_UPWARD := 16r0800. >> FE_TOWARDZERO := 16r0C00. >> "For some reasons we have to call fegetround once." >> "c := LibC new fegetround." >> LibC new fesetround: FE_DOWNWARD. >> (Delay forSeconds: 1) wait. >> v1 := 1.0/10.0. >> LibC new fesetround: FE_UPWARD. >> v2 := 1.0/10.0. >> LibC new fesetround: FE_TONEAREST. >> v1 < v2. >> >> If the delay is inserted, the script evaluates to false. Using the same >> LibC-instance or creating a new one does not seem to change anything >> here. >> Interestingly, a similar approach in VisualWorks does not show this >> issue >> yet. >> >> > âOk, so maybe we need to use put evaluation in a block and use > valueNoContextSwitch ? > âMaybe use an API like the one you propose before : > Double roundToMinusInfWhile: [ ... ] > > > >> Actually, I expect the FE_* macros to be platform/implementation >> dependent, as suggested here: >> >> http://www.enseignement.polytechnique.fr/informatique/INF478/docs/Cpp/en/c/… >> >> > âOk. > > Can we try to pack everything in a PR for Pharo 7.0 ? > âThank you.

May 29, 2018

Re: [Pharo-users] Problem with PharoLauncher on Ubuntu 18.04 (64 bit)

by Francisco Lizarralde

Hi Francisco, > Le 29 mai 2018 Ã 00:30, Francisco Lizarralde <francisco.lizarralde@> > a Ã©crit : > > Hi all, > > I was using the PharoLauncher (32 bits) version on Ubuntu 14.04 (32 bits) > without problem. But two days ago I installed Ubuntu 18.04 (64 bits) and > tried to run PharoLauncher-linux-1.1-x64 and when I tried to run a 6.1 > image It is not very surprising that you get problems when using 32-bits pharo version on an new 64-bits system. With time, it is more and more difficult to find compatible 32-bits libraries to install on these systems. Did you follow instructions available at https://pharo.org/gnu-linux-installation? Hi Christophe, Thank you for your prrompt reply. Before I had a 32 bit PharoLauncher running on a 32 bit Ubuntu without problem and now I do not have a 32 bit of PharoLauncher running on a Ubuntu 18.04. But now I have installed an all new 64 bit version of Ubuntu 18.04 and then decompressed the PharoLauncher-linux-1.1-x64.zip and is with this version that I have problems to run a 6.1 image. I think the problem would be that PharoLauncher doesn't locate the path of libc.so "Error. Could not determine platform's libc path for VM. Try forcing $PLATFORMLIBDIR in /home/francisco/Pharo/vms/private/6521/pharo, based on LIBC_SO." But I don't know how to fix it. I will try to post the issue at https://github.com/pharo-project/pharo-launcher/issues Best regards. Francisco -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

May 29, 2018

[ANN] Iceberg v1.0.0

by Guillermo Polito

Hi all, Time for a new Iceberg update, that will be available in the next Pharo build. This time, there are lots of cleanups and enhancements. On the big highlights: - Tonel migration plugin is available in the "Other menu item" - Tests are green on 64 bits! (meaning iceberg can be safely used in 64 bits). Thanks to everybody that participated in reviewing, opening/closing issues or even fixing a typo! # Documentation Just as a reminder, here you have a link to iceberg's wiki, convering some info like terminology, how to help us, and so on... https://github.com/pharo-vcs/iceberg/wiki # And some videos ;) - Branching and merging https://www.youtube.com/watch?v=DBzkjwABPEI - Loading a Baseline https://youtu.be/brUHEOr-p_E - Contributing to Iceberg https://youtu.be/yGr5HvVWM0M # Changes Log https://github.com/pharo-vcs/iceberg/releases/tag/v1.0.0 Enjoy, Guille PS, detailed changes log below: # Cleanups #819 Fix tooltip typo in settings #800 Iceberg should be removed from the catalogue #801 Remove not referenced packages #803 Correct some lints in tests #806 Bad repair options when local repository is missing #725 Remove and clean old UI #794 Some classes should use category "utilities" instead of "utility" #791 Begin to remove old UI #734 Begin to remove old UI #576 Add link to github/gitlab ssh instructions # Enhancements #776 Upgrade to Commander 0.6.2 dependencies #765 Add command to copy SHA from history window #793 Add the commit message to history window #785 Metacello conflicts are not handled Metacello Integration # Bug fixes #771 IceTipRemoveFromRepositoryPackageCommand >> execute is not implemented #748 Code subdirectory in empty repository #767 Error while pulling with renamed packages #814 Moving extension from a package removes extended class #807 When we do not have the right to push on a report we get an Error instead of the pop up! #768 Inverse merge preview shows wrong diff #784 Pulling from a non existing remote branch fails#810 #removePackage: should recursively delete files # Documentation #702 Create screencast - How to contribute to iceberg #774 Copy Wiki contribution page to pharo-project/pharo wiki # Infrastructure #761 Make tests run in 64 bits Pharo 7

May 29, 2018

Re: [Pharo-users] Problem with PharoLauncher on Ubuntu 18.04 (64 bit)

by Christophe Demarey

Hi Francisco, > Le 29 mai 2018 Ã 00:30, Francisco Lizarralde <francisco.lizarralde(a)gmail.com> a Ã©crit : > > Hi all, > > I was using the PharoLauncher (32 bits) version on Ubuntu 14.04 (32 bits) > without problem. But two days ago I installed Ubuntu 18.04 (64 bits) and > tried to run PharoLauncher-linux-1.1-x64 and when I tried to run a 6.1 image It is not very surprising that you get problems when using 32-bits pharo version on an new 64-bits system. With time, it is more and more difficult to find compatible 32-bits libraries to install on these systems. Did you follow instructions available at https://pharo.org/gnu-linux-installation? Prepare 64-bit-Linux for 32bit Pharo The installation in Debian 8 Jessie 64bits and Ubuntu 14.04 and Later require some operations. sudo dpkg --add-architecture i386 sudo apt-get update sudo apt-get install libx11-6:i386 sudo apt-get install libgl1-mesa-glx:i386 sudo apt-get install libfontconfig1:i386 sudo apt-get install libssl1.0.0:i386 I would recommend you to use the 64-bits version of PharoLauncher: http://files.pharo.org/pharo-launcher/1.1/PharoLauncher-linux-1.1-x64.zip Tell me if it is ok. If not, do not hesitate to post an issue: https://github.com/pharo-project/pharo-launcher/issues Regards, Christophe. > I got this message. > > Try this on a terminal: > > cd "/home/francisco/Pharo/vms/private/6521" && export SQUEAK_PLUGINS="" && > "/home/francisco/Pharo/vms/private/6521/pharo" --nodisplay > "/home/francisco/Pharo/images/Pharo 6.1 (stable)_1/Pharo 6.1 > (stable)_1.image" eval "(Smalltalk imagePath asFileReference parent) / > 'pharo.version' writeStreamDo: [ :stream | |major minor|major := > SystemVersion current major.minor := SystemVersion current minor.(major = 6 > and: [ SystemVersion current highestUpdate >= 60509 ])ifTrue: [ minor := 1 > ].stream << major asString;<< minor asString ]" > > And got this: > > Error. Could not determine platform's libc path for VM. > Try forcing $PLATFORMLIBDIR in /home/francisco/Pharo/vms/private/6521/pharo, > based on LIBC_SO. > Please report what works to pharo [vm-dev] mail list. > LIBC_SO= > DISTRIB_ID=Ubuntu > DISTRIB_RELEASE=18.04 > DISTRIB_CODENAME=bionic > DISTRIB_DESCRIPTION="Ubuntu 18.04 LTS" > NAME="Ubuntu" > VERSION="18.04 LTS (Bionic Beaver)" > ID=ubuntu > ID_LIKE=debian > PRETTY_NAME="Ubuntu 18.04 LTS" > VERSION_ID="18.04" > VERSION_CODENAME=bionic > UBUNTU_CODENAME=bionic > UNAME=Linux Dynabook 4.15.0-22-generic #24-Ubuntu SMP Wed May 16 12:15:17 > UTC 2018 x86_64 x86_64 x86_64 GNU/Linux > System seems to be 64 bit. You may need to (re)install the 32-bit > libraries. > > Do I really need to install 32-bit libraries ? > > Any advice will be apreciated !!! > > Thanks in advance, > > Francisco > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

May 29, 2018

Problem with PharoLauncher on Ubuntu 18.04 (64 bit)

by Francisco Lizarralde

Hi all, I was using the PharoLauncher (32 bits) version on Ubuntu 14.04 (32 bits) without problem. But two days ago I installed Ubuntu 18.04 (64 bits) and tried to run PharoLauncher-linux-1.1-x64 and when I tried to run a 6.1 image I got this message. Try this on a terminal: cd "/home/francisco/Pharo/vms/private/6521" && export SQUEAK_PLUGINS="" && "/home/francisco/Pharo/vms/private/6521/pharo" --nodisplay "/home/francisco/Pharo/images/Pharo 6.1 (stable)_1/Pharo 6.1 (stable)_1.image" eval "(Smalltalk imagePath asFileReference parent) / 'pharo.version' writeStreamDo: [ :stream | |major minor|major := SystemVersion current major.minor := SystemVersion current minor.(major = 6 and: [ SystemVersion current highestUpdate >= 60509 ])ifTrue: [ minor := 1 ].stream << major asString;<< minor asString ]" And got this: Error. Could not determine platform's libc path for VM. Try forcing $PLATFORMLIBDIR in /home/francisco/Pharo/vms/private/6521/pharo, based on LIBC_SO. Please report what works to pharo [vm-dev] mail list. LIBC_SO= DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04 LTS" NAME="Ubuntu" VERSION="18.04 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04 LTS" VERSION_ID="18.04" VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic UNAME=Linux Dynabook 4.15.0-22-generic #24-Ubuntu SMP Wed May 16 12:15:17 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux System seems to be 64 bit. You may need to (re)install the 32-bit libraries. Do I really need to install 32-bit libraries ? Any advice will be apreciated !!! Thanks in advance, Francisco -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

May 28, 2018

Re: [Pharo-users] Code completion in Pharo?

by phil＠highoctane.be

Try Cmd-q or Ctrl-q ( and right alt click on Windows). Spotter also has suffixes like #im #cl #sen to be put after a few keystrokes. Spotter: shift-enter (who knows). Phil On Sat, May 26, 2018, 22:16 Tim Mackinnon <tim(a)testit.works> wrote: > Thatâs exactly the exploratory attitude we like to see... > > I think the code completer is pluggable and can be selected in the > settings (I think there are 2, and their history is probably in this list > somewhere), so you can try your own too. > > Tim > > Sent from my iPhone > > > > Sent from my iPhone > On 26 May 2018, at 16:10, Andrzej Olszak <andrzej.olszak(a)gmail.com> wrote: > > Hi Tim and Nicole, > > Thanks for great tips. The click+keyModifier actions are extremely useful, > and combined with breakpoints make for a great way of 'peeking under the > hood' of the existing features. > > Also, I've just found a perfect piece of real code to do some learning and > experimenting on - it will be the code completion itself! ;-) > > Andrzej > > On Fri, May 25, 2018 at 10:47 AM, Nicole de Graaf <nic(a)soops.nl> wrote: > >> Hi Andrzej, >> >> my way of doing it: >> >> Searching in the image what other guys are doing. >> >> Finder: asMorph >> >> and here you can find methods like >> >> #openAsMorph .. you can get a clue. >> >> or: >> >> âsome textâ asMorph inspect .. >> than you get the object and you can search the class and from here the >> class the references. >> >> *All my steps are based on code reading not code completion.* >> >> Code completion I use more if I know what is should be and use the same >> method names as the other developers. >> >> Nic >> >> >> On 25 May 2018, at 03:12, andreo <andrzej.olszak(a)gmail.com> wrote: >> >> Dear Pharoers, >> >> I'm just starting out with Pharo 6.1, and I'm trying to use code >> completion >> to interactively explore various objects and their messages. However, I'm >> having difficulties doing this efficiently - I think I must be missing >> something obvious, and I hope you can point me in the right direction. >> >> For instance, let's say I have the below in Playground: >> >> 'some text' asMorph >> >> and I would like to display the morph object as a window, but I don't know >> the exact message name, or whether such a message exists at all. If I type >> "Window", then the completion popup will show a long list of matching >> messages, but won't show their documentation or argument names, so it will >> be difficult to know exactly what these messages do. >> I can see that one can do "Do it and go" on an expression and then browse >> the available messages in Meta, but maybe there is simpler/faster way? >> >> How would an experienced Pharo user typically go about discovering the >> right >> messages in such situations? >> >> Best regards, >> Andrzej >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >> >> >

May 26, 2018