February 2017 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

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

Feb. 23, 2017

Re: [Pharo-dev] Build Pharo VM

by Esteban Lorenzano

> On 23 Feb 2017, at 15:33, Guido Chari <charig(a)gmail.com> wrote: > > Hi, > > I am trying to compile the Pharo-VM but I was not able. Neither in OSX nor in Unix. I followed the instructions on https://github.com/pharo-project/pharo-vm <https://github.com/pharo-project/pharo-vm>. In OSX the builder at the image level runs ok but I see no output at the build directory. In Unix, the files in the build directory were generated but then the building process fails because of some cmake files not found from one of the plugins. I am using the last version from the master repo. > > So my question is, any hints on what I am doing wrong? Are there any up to date documentation for building the vm? yes: everything :) that instructions are very old and I still do not have time to fix themâ¦ basically, if all your dependencies are ok, doing this should be enough: $ git clone git@github.com:pharo-project/pharo-vm.git $ cd pharo-vm/opensmalltalk-vm/build.macos32x86/pharo.cog.spur $ ./mvm -f for linux you can: $ cd pharo-vm/opensmalltalk-vm//build.linux32x86/pharo.cog.spur/build $ ./mvm Esteban > > Best regards, > Guido.

Feb. 23, 2017

Re: [Pharo-dev] Any idea for a cool name for the remote tool suite?

by Ben Coman

Not great but okay. i think we are at the point of "perfect is the enemy of done". There have been plenty of suitable suggestions, and its a topic with high bike-shedding quotient, so you should just pick one you and the man paying the bills are happy with. Otherwise you'll get another round of suggestions like these... "phrem" 26k googs - pharo remote "phremt" - 195 googs - pharo remote tools "phremit" 225 googs - pharo remote integrated tools "phremide" 5 googs - pharo remote ide One thing to keep in mind though is that we can be as clever as we like here in text, but you should imagine yourself saying it in front of a lecture. cheers -ben On Thu, Feb 23, 2017 at 5:35 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Philippe invented new word Pharocket :). Maybe it is the best for this > project? > > > 2017-01-30 17:09 GMT+01:00 Dimitris Chloupis <kilon.alios(a)gmail.com>: > >> Also I think its fair that the guy that wrote the code to pick the name, >> its his baby afterall, whether he is paid for it or not. He earned that >> right. >> >> On Mon, Jan 30, 2017 at 6:06 PM Dimitris Chloupis <kilon.alios(a)gmail.com> >> wrote: >> >>> Just for the record, the name does not matter >>> >>> As a matter of fact if you want the name to really sell the library/ >>> tools then the last thing you want is a name that makes any logical sense >>> >>> You have much better chance to catch attention with "Pink Elephant" than >>> "Pharo Remote tools" or whatever >>> >>> illogical names monopolise the software market >>> >>> Python >>> Ruby on Rails >>> Django >>> Blender >>> Unreal >>> Unity >>> Javascript >>> Java >>> C >>> C++ >>> Windows >>> MacOS >>> >>> and so on >>> >>> Developers choose to name their projects the craziest names and wisely so >>> >>> the name is there to catch attention, not to make sense or come up top >>> on google search. >>> >>> In the end what it matters is the code itself. >>> >>> Ruby On Rails did not become populary because we love ruby stones or we >>> love go "too...tooooooo" on rails ... its popular because the library has >>> been very useful to many people. >>> >>> And the name itself guarantees that it wont come up top in google search >>> because it has nothing unique about it. >>> >>> The rest is just marketing ;) >>> >> >

Feb. 23, 2017

Build Pharo VM

by Guido Chari

Hi, I am trying to compile the Pharo-VM but I was not able. Neither in OSX nor in Unix. I followed the instructions on https://github.com/pharo-project/pharo-vm. In OSX the builder at the image level runs ok but I see no output at the build directory. In Unix, the files in the build directory were generated but then the building process fails because of some cmake files not found from one of the plugins. I am using the last version from the master repo. So my question is, any hints on what I am doing wrong? Are there any up to date documentation for building the vm? Best regards, Guido.

Feb. 23, 2017

Re: [Pharo-dev] Pharo Papers

by denker

Hello, I have setup a collection at HAL. For now it is empty, we should fill it and then add it to the website (and announce it then, not nowâ¦). The collection automatically has every paper on HAL that has âPHAROâ as a keyword in the field "Project/Collaborationâ. https://hal.inria.fr/PHARO/ https://hal.archives-ouvertes.fr/PHARO HAL is not Inria specific, here is some more infos (from https://hal.archives-ouvertes.fr ): HAL is an open archive where authors can deposit scholarly documents from all academic fields. For the attention of the authors â¢ The deposit must be made in agreement with the co-authors and in the respect for the policy of the publishers. â¢ The deposit is subject of a control, HAL reserves the right to refuse items that do not meet the criteria of the archive. â¢ Any deposit is definitive, no withdrawals will be made after the on-line posting of the publication. â¢ Text files in pdf format or image files are sent to CINES (https://www.cines.fr/en/) for long-term archiving. For the attention of the readers â¢ In a context of electronic distribution, every author keep all its intellectual property rights. > On 16 Feb 2017, at 15:13, denker <marcus.denker(a)inria.fr> wrote: > > One idea on my TODO that I got from colleagues here working on another OpenSource/Research > system (Sofa3D): to add all publication to the website automatically using HAL (the national french > paper database). > > It looks like this on the website: > https://www.sofa-framework.org/applications/publications/ > > and here âhow to add a paperâ: > > https://www.sofa-framework.org/applications/publications/add-a-publication-… > > I will definitely set this up for Pharo later this year (read: as soon as possible) > > Marcus > > >> On 16 Feb 2017, at 14:30, Ben Coman <btc(a)openinworld.com> wrote: >> >> And now for your regularly scheduled random trivia show... >> I was mildly curious about how many papers touched on Pharo. >> >> 1,110 on google scholar for... >> "pharo" "programming" >> http://tiny.cc/pharo-scholar >> >> 1,630 on normal google for... >> "pharo" "programming" "abstract" "introduction" "conclusion" >> "references" filetype:pdf >> http://tiny.cc/pharo-papers >> >> Probably a lot of overlap between them. >> cheers -ben >> >

Feb. 23, 2017

Re: [Pharo-dev] Any idea for a cool name for the remote tool suite?

by Denis Kudriashov

Philippe invented new word Pharocket :). Maybe it is the best for this project? 2017-01-30 17:09 GMT+01:00 Dimitris Chloupis <kilon.alios(a)gmail.com>: > Also I think its fair that the guy that wrote the code to pick the name, > its his baby afterall, whether he is paid for it or not. He earned that > right. > > On Mon, Jan 30, 2017 at 6:06 PM Dimitris Chloupis <kilon.alios(a)gmail.com> > wrote: > >> Just for the record, the name does not matter >> >> As a matter of fact if you want the name to really sell the library/ >> tools then the last thing you want is a name that makes any logical sense >> >> You have much better chance to catch attention with "Pink Elephant" than >> "Pharo Remote tools" or whatever >> >> illogical names monopolise the software market >> >> Python >> Ruby on Rails >> Django >> Blender >> Unreal >> Unity >> Javascript >> Java >> C >> C++ >> Windows >> MacOS >> >> and so on >> >> Developers choose to name their projects the craziest names and wisely so >> >> the name is there to catch attention, not to make sense or come up top on >> google search. >> >> In the end what it matters is the code itself. >> >> Ruby On Rails did not become populary because we love ruby stones or we >> love go "too...tooooooo" on rails ... its popular because the library has >> been very useful to many people. >> >> And the name itself guarantees that it wont come up top in google search >> because it has nothing unique about it. >> >> The rest is just marketing ;) >> >

Feb. 23, 2017

Re: [Pharo-dev] WeakValueDictionary: shouldn't be "absent" after GC?

by Guillermo Polito

Thanks Martin :) On Thu, Feb 23, 2017 at 6:18 AM, Martin Dias <tinchodias(a)gmail.com> wrote: > > > On Wed, Feb 22, 2017 at 9:52 AM, Guillermo Polito < > guillermopolito(a)gmail.com> wrote: > >> >> >> On Wed, Feb 22, 2017 at 12:57 AM, Martin Dias <tinchodias(a)gmail.com> >> wrote: >> >>> Hi all >>> >>> Phil: >>> I'm sorry, didn't get what you point with the code snippet. The copy of >>> the Symbol is the same instance, that I think it's nto GCed. >>> >>> Guille: >>> Yes, I knew the internals of the WeakValueDictionary but asked about the >>> API. >>> >> >> Ah, ok, I only understood that you did not get why it was like that. :) >> >> >>> What I don't know is about using WeakRegistry >>> >> >> This is just needed to do the cleanup of the expired associations. >> >> >>> and Ephemerons. >>> >> >> This is a completely different thing. There is an EphemeronRegistry in >> the image, but it does not propose at:/at:ifAbsent: messages. It just holds >> Ephemerons. >> >> I'll check WeakKeyDictionary. >>> >> >> If you need to hold weakly the values, then this is not what you're >> looking for, isn't it? >> >> >>> >>> I understand the idea of "explicit control of magic", but not sure if I >>> understand concretely. Do you mean to implement something like >>> WeakValueDictionary>>register which will not be executed by >>> #initialize, so the user can decide to register. Am I right? >>> >> >> Yep. I would even call it: >> >> registerForCleanup >> >> Like that it is explicit that you're doing it, and that it may incur into >> some performance degradation of the entire system. >> >> >>> >>> Denis: >>> +1 WeakSet behavior is really confusing! In thte case of >>> WeakValueDictionary I didn't check for inconsistencies but was only annoyed >>> but it's behavior. >>> >>> Guille and Denis: >>> Instead of using SetElement or cleaning up the empty >>> WeakValueAssociations, what I first thought is to internally consider an >>> association with nil as absent. I mean, modify or override some methods >>> soem when there is an WeakValueAssociation with value == nil it >>> considers it's absent. Concretely, I'd expect: >>> >> >> Well, the idea of the SetElement is that you may want to have `nil` as a >> valid value in your dictionary. Otherwise, you cannot do: >> >> WeakValueDictionary new >> at: 'key' put: nil; >> at: 'key' --> error??? >> >> We can discuss if it is useful or not, but as with sets, before people >> used to check if the inserted element was nil beforehand to have the >> expected behavior... >> >> >>> | dictionary | >>> dictionary := WeakValueDictionary with: 'hello' -> 'world' copy. >>> Smalltalk garbageCollect. >>> { >>> dictionary values includes: nil. *---> false * >>> dictionary at: 'hello'. * ---> NotFound signal* >>> dictionary at: 'hello' ifAbsent: [ 'absent' ].* ---> 'absent'* >>> dictionary at: 'hello' ifAbsentPut: [ 'put' ]. *---> 'put'* >>> } >>> >> >> I agree that we may review the API. At least #at:, #at:ifAbsent: and >> #at:ifAbsentPut: should behave similarly. >> >> > OK, I wrote several tests for the expected behavior and fixed > WeakValueDictionary. Anyway, not sure if it's convenient to integrate it in > Pharo 6 or in any version... maybe it's just OK to check for nils at > user-level as currently, and do not change it. I had to use SetElement else > tests didn't pass. > > https://pharo.fogbugz.com/f/cases/19746/WeakValueDictionary-has- > counter-intuitive-behavior > > > > >> In any case, we could see how to improve EphemeronRegistry or even >> implement an EphemericDictionary that would replace the WeakValueDictionary. >> >> >>> >>> It's better if I give some context. Look this simplified version of my >>> use case: >>> >>> MyUI>> >>> morphAt: key >>> cache ifNil: [ cache := WeakValueDictionary new ]. >>> ^ cache at: key ifPresent: [:cachedValueOrNil | cachedValueOrNil >>> ifNotNil: [ cachedValueOrNil ] ifNil: [ cache at: entryReference put: (self >>> newMorph: key) ] ] ifAbsent: [ cache at: entryReference put: (self >>> newMorph: key) ] >>> >>> I'd like to only send #newMorph: in ifAbsent: and to avoid the >>> ifNotNil:ifNil: >>> Like this: >>> >>> morphAt: key >>> cache ifNil: [ cache := WeakValueDictionary new ]. >>> ^ cache at: key ifAbsent: [ cache at: entryReference put: (self >>> newMorph: key) ] >>> >>> :-) >>> >>> MartÃn >>> >> >> >

Feb. 23, 2017

Re: [Pharo-dev] WeakValueDictionary: shouldn't be "absent" after GC?

by Martin Dias

On Wed, Feb 22, 2017 at 9:52 AM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > > > On Wed, Feb 22, 2017 at 12:57 AM, Martin Dias <tinchodias(a)gmail.com> > wrote: > >> Hi all >> >> Phil: >> I'm sorry, didn't get what you point with the code snippet. The copy of >> the Symbol is the same instance, that I think it's nto GCed. >> >> Guille: >> Yes, I knew the internals of the WeakValueDictionary but asked about the >> API. >> > > Ah, ok, I only understood that you did not get why it was like that. :) > > >> What I don't know is about using WeakRegistry >> > > This is just needed to do the cleanup of the expired associations. > > >> and Ephemerons. >> > > This is a completely different thing. There is an EphemeronRegistry in the > image, but it does not propose at:/at:ifAbsent: messages. It just holds > Ephemerons. > > I'll check WeakKeyDictionary. >> > > If you need to hold weakly the values, then this is not what you're > looking for, isn't it? > > >> >> I understand the idea of "explicit control of magic", but not sure if I >> understand concretely. Do you mean to implement something like >> WeakValueDictionary>>register which will not be executed by #initialize, >> so the user can decide to register. Am I right? >> > > Yep. I would even call it: > > registerForCleanup > > Like that it is explicit that you're doing it, and that it may incur into > some performance degradation of the entire system. > > >> >> Denis: >> +1 WeakSet behavior is really confusing! In thte case of >> WeakValueDictionary I didn't check for inconsistencies but was only annoyed >> but it's behavior. >> >> Guille and Denis: >> Instead of using SetElement or cleaning up the empty >> WeakValueAssociations, what I first thought is to internally consider an >> association with nil as absent. I mean, modify or override some methods >> soem when there is an WeakValueAssociation with value == nil it >> considers it's absent. Concretely, I'd expect: >> > > Well, the idea of the SetElement is that you may want to have `nil` as a > valid value in your dictionary. Otherwise, you cannot do: > > WeakValueDictionary new > at: 'key' put: nil; > at: 'key' --> error??? > > We can discuss if it is useful or not, but as with sets, before people > used to check if the inserted element was nil beforehand to have the > expected behavior... > > >> | dictionary | >> dictionary := WeakValueDictionary with: 'hello' -> 'world' copy. >> Smalltalk garbageCollect. >> { >> dictionary values includes: nil. *---> false * >> dictionary at: 'hello'. * ---> NotFound signal* >> dictionary at: 'hello' ifAbsent: [ 'absent' ].* ---> 'absent'* >> dictionary at: 'hello' ifAbsentPut: [ 'put' ]. *---> 'put'* >> } >> > > I agree that we may review the API. At least #at:, #at:ifAbsent: and > #at:ifAbsentPut: should behave similarly. > > OK, I wrote several tests for the expected behavior and fixed WeakValueDictionary. Anyway, not sure if it's convenient to integrate it in Pharo 6 or in any version... maybe it's just OK to check for nils at user-level as currently, and do not change it. I had to use SetElement else tests didn't pass. https://pharo.fogbugz.com/f/cases/19746/WeakValueDictionary-has-counter-int… > In any case, we could see how to improve EphemeronRegistry or even > implement an EphemericDictionary that would replace the WeakValueDictionary. > > >> >> It's better if I give some context. Look this simplified version of my >> use case: >> >> MyUI>> >> morphAt: key >> cache ifNil: [ cache := WeakValueDictionary new ]. >> ^ cache at: key ifPresent: [:cachedValueOrNil | cachedValueOrNil >> ifNotNil: [ cachedValueOrNil ] ifNil: [ cache at: entryReference put: (self >> newMorph: key) ] ] ifAbsent: [ cache at: entryReference put: (self >> newMorph: key) ] >> >> I'd like to only send #newMorph: in ifAbsent: and to avoid the >> ifNotNil:ifNil: >> Like this: >> >> morphAt: key >> cache ifNil: [ cache := WeakValueDictionary new ]. >> ^ cache at: key ifAbsent: [ cache at: entryReference put: (self >> newMorph: key) ] >> >> :-) >> >> MartÃn >> > >

Feb. 23, 2017

Re: [Pharo-dev] UnixOSProcessPlugin and accessing C array out of bounds

by David T. Lewis

Holger, Good catch, thank you. There were two arrays dimensioned wrong in OSProcessPlugin in the Smalltalk slang source. I fixed this, and the warning should be gone after the sources are next generated. Esteban, I fixed the oscog branch also. I could not easily test it, but it is a small change so hopefully should be no problem when you next generate the plugin. Dave On Wed, Feb 22, 2017 at 04:25:05PM +0700, Holger Freyther wrote: > Hi Esteban, > > while building packages for OBS and going the compile warnings (one of the nice things of newer compilers is the increased diagnostic) I noticed this: > > [ 196s] /usr/src/packages/BUILD/src/plugins/UnixOSProcessPlugin/UnixOSProcessPlugin.c:4525:20: warning: iteration 64u invokes undefined behavior [-Waggressive-loop-optimizations] > [ 196s] if ((semaIndices[sigNum]) > 0) { > [ 196s] ^ > [ 196s] /usr/src/packages/BUILD/src/plugins/UnixOSProcessPlugin/UnixOSProcessPlugin.c:4524:9: note: containing loop > [ 196s] while (sigNum <= (signalArraySize())) { > > while (sigNum <= (signalArraySize())) { > if ((semaIndices[sigNum]) > 0) { > setSignalNumberhandler(sigNum, (originalSignalHandlers())[sigNum]); > } > sigNum += 1; > } > > semaIndices has signalArraySize()/NSIG number of entries and is zero based, it is being accessed with sigNum==NSIG which means one entry beyond the memory of the array? Can you confirm this? > > restoreDefaultSignalHandlers > "Restore signal handlers to their original behaviors." > > | sigNum | > <returnTypeC: 'void'> > semaIndices = nil "nil if in interpreter simulation" > ifFalse: [sigNum := 1. > [sigNum <= self signalArraySize] whileTrue: > [((semaIndices at: sigNum) > 0) ifTrue: > [self setSignalNumber: sigNum handler: (self originalSignalHandlers at: sigNum).]. > sigNum := sigNum + 1]] > > So it is one based but the array doesn't have an extra element to make it work? How is this normally handled in slang code? > > > holger

Feb. 23, 2017

Re: [Pharo-dev] [Moose-dev] Re: How ready is Bloc for a simple use-case?

by Peter Uhnak

I'm happy to hear that. I understand that Bloc is low-level, but I wanted to start getting familiar with it (Roassal3 should eventually be on top of it, so I need to understand the basics anyway). > It is very doable. Please, don't forget that Bloc is a low level framework > that does not contain any widgets (existing ones will be deleted, > especially BlLine, BlText and BlTextElement). I am not sure how am I to interpret removal of BlText and BlTextElement. Does this mean that I would have to compose characters (is there BlCharacter) by myself? (I am not sure what the complexity implications are). But I am happy that all the things are in place, so I can slowly (weeks, months) start playing with it. Thanks! Peter On Wed, Feb 22, 2017 at 10:02:28PM +0100, Aliaksei Syrel wrote: > Hi Peter > > I wanted to ask about Bloc: > > Thanks for your interest :) > > 1) how stable is the API? e.g. if some overhaul changes to unify/whatever > > are planned > > > Api itself is in "final" state, however naming might be improved (changed > with or without depreciations). But don't worry user-side api is already in > a very good shape, at least from our perspective :) > > 2) I saw in the techtalk that you can align elements (to center, bottom, > > ...), however is that possible with lines? Lines have to rotate, morph > > shape, etc. > > 3) Are non-straight lines possible? (e.g. bezier, arc) > > > Exactly :) Lines are just bloc elements as anything else: buttons, text > images. They can be linear, can be arcs or bezier curves (both quadratic or > cubic). Default canvas used for rendering in Bloc (SpartaCanvas) has very > good support of vector shapes and lines. > > The idea for me is to make a simple mindmap > > - elements with some text, icons, math symbols inside > > - connectors (non-straight lines) between elements > > > It is very doable. Please, don't forget that Bloc is a low level framework > that does not contain any widgets (existing ones will be deleted, > especially BlLine, BlText and BlTextElement). The only responsibility Bloc > has is to provide a basic infrastructure that does not put any constraints > on users. Which means that if you want to have a bezier line you have to > subclass BlElement, implement corresponding accessors for anchor points and > override drawPathOnSpartaCanvas: in order to display you line. You can > learn more about canvas by checking SpartaCanvas class comment and method > comments in 'api' protocol. > > Layouts, alignment, transformations are part of bloc and are available to > all subclasses of BlElement. > > Cheers, > Alex > > On 22 February 2017 at 21:32, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > > > Hi, > > > > I wanted to ask about Bloc: > > > > 1) how stable is the API? e.g. if some overhaul changes to unify/whatever > > are planned > > 2) I saw in the techtalk that you can align elements (to center, bottom, > > ...), however is that possible with lines? Lines have to rotate, morph > > shape, etc. > > 3) Are non-straight lines possible? (e.g. bezier, arc) > > > > The idea for me is to make a simple mindmap > > - elements with some text, icons, math symbols inside > > - connectors (non-straight lines) between elements > > > > To me (apart from the lines) it seems like it should be already doable. > > > > Also either my (Morphic) Pharo is really slow, or Bloc (in the video) is > > superfast (everything is happening instantly). > > > > Thanks, > > Peter > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)list.inf.unibe.ch > > https://www.list.inf.unibe.ch/listinfo/moose-dev > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev

Feb. 22, 2017