- Pharo-dev - lists.pharo.org

Pavel's ChangeLog week of 2018-02-05

by Pavel Krivanek

Hi, among other less interesting things, I spent some time on existing PosixSharedMemory project. It is a UFFI binding for the LibC methods that provide support for the memory allocation between several separate processes. I significantly improved the performance by implementing the block access. Writing of 10MB byte array takes about 1 millisecond, reading of it from other image took me about 4 milliseconds. While serialization with Fuel is very fast, it opens interesting possibilities. To have a shared memory without synchronization tools is not very useful so I wrote a basic UFFI interface for the POSIX named semaphores. They are quite easy to use and work nicely with Pharo. The VM can all wait on the semaphore or it can check the status of it periodically in an image thread. It has two small disadvantages. It requires to dynamically link the next library (pthread) and they must be cleaned manually. I plan to look at System V alternative in future. Now we should write a nice framework for inter-image communication on top of it or/and adopt Seamless for it ;-) Cheers, -- Pavel

Feb. 12, 2018

[Pharo 7.0-dev] Build #531: 21297 Remove unnecessary "self run:" in SortedCollectionTest

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #531 was: SUCCESS. The Pull Request #859 was integrated: "21297 Remove unnecessary "self run:" in SortedCollectionTest" Pull request url: https://github.com/pharo-project/pharo/pull/859 Issue Url: https://pharo.fogbugz.com/f/cases/21297 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 12, 2018

Re: [Pharo-dev] Iceberg experience report - synchronising README change made on github

by Guillermo Polito

On Thu, Feb 8, 2018 at 6:28 AM, Ben Coman <btc(a)openinworld.com> wrote: > Could the Iceberg gurus try and comment on the following workflow. > > Please familiarise with the first four commits here... > https://github.com/Traadh/cloudflareun/network > > from these actions... > > "first commit" -- on github I created it as an unitialized repo to try > to push a "new repo" to it per my other post, but when that failed > from the command line I did `git init; git add README; git remote ...; > git push ...`) > > "First Pharo code" -- cloned the repo with Iceberg, added a package, > synchronised, added commit comment and clicked <Commit and push onto > master> > > "Update class comment" -- edited the class comment, then from Iceberg > synchronised, added commit comment and clicked <Commit and push onto > master> > > "Updated README" -- on github, used the built-in editor to easily > preview markdown. Clicked its <Commit directly to the master branch.> > > > PROBLEM... > > Now I'm at a point having trouble synchronising Iceberg to pick up > that last change. > 1. Right-clicked on "cloudflareun" and chose "Synchronise repository..." > 2. In [Update] tab, clicked <Fetch new versions> > and listed under [commits to be imported] is "Updated README". Good. > 3. Then clicked on <Pull> which I expected would load that commit into > the Image, > and a new commit "Merge with ref/remotes/origin/master" showed up in > [commit to be imported] > > So now I'm lost. > It seems the <Pull> only operates on the disk? > But why does it create a merge commit? > It should have fast-forwarded. > Checking from the command line, only shows the first three commits are > common with the github network graph. The fourth commit is the new > merge commit. > $ git log > commit f49c64a7751f95712acc30dab692fc7e85e0c810 > Merge: c818e9a 52ab6ac > Author: Ben Coman <btc(a)openInWorld.com> > Date: Thu Feb 8 11:55:34 2018 +0800 > Merge with refs/remotes/origin/master > > commit c818e9adebeb6be001b202aa48da009be97920eb > Author: Ben Coman <btc(a)openInWorld.com> > Date: Thu Feb 8 11:42:57 2018 +0800 > Update class comment. > > commit 6f2df89b219c56530412252ace96bc95eb78373a > Author: Ben Coman <btc(a)openInWorld.com> > Date: Thu Feb 8 11:37:01 2018 +0800 > First Pharo code > > commit 52ab6ac696760a60fe56af57e45f2e2ceaaae35e > Author: Ben Coman <btc(a)openInWorld.com> > Date: Thu Feb 8 11:31:28 2018 +0800 > first commit > > Checking the remote... > $ git log origin/master > commit 52ab6ac696760a60fe56af57e45f2e2ceaaae35e > Author: Ben Coman <btc(a)openInWorld.com> > Date: Thu Feb 8 11:31:28 2018 +0800 > first commit > > Whoops... not what I expected but I don't think that affected anything > now. Probably it was left over from early attempts to create a "new" > "cloudflareun" repo. > > Try again... > $ git remote --v > origin git@github.com:Traadh/cloudflareun.git (fetch) > origin git@github.com:Traadh/cloudflareun.git (push) > traadh git@github.com:Traadh/cloudflareun.git (fetch) > traadh git@github.com:Traadh/cloudflareun.git (push) > > $ git log traadh/master > commit 587bed95c4b8fb3986c9962c9206405c81c99e3d > Author: Ben Coman <github.com(a)ben.coman.com.au> > Date: Thu Feb 8 11:54:20 2018 +0800 > Updated README > > commit c818e9adebeb6be001b202aa48da009be97920eb > Author: Ben Coman <btc(a)openInWorld.com> > Date: Thu Feb 8 11:42:57 2018 +0800 > Update class comment. > > commit 6f2df89b219c56530412252ace96bc95eb78373a > Author: Ben Coman <btc(a)openInWorld.com> > Date: Thu Feb 8 11:37:01 2018 +0800 > First Pharo code > > commit 52ab6ac696760a60fe56af57e45f2e2ceaaae35e > Author: Ben Coman <btc(a)openInWorld.com> > Date: Thu Feb 8 11:31:28 2018 +0800 > first commit > > So there are the four commits matching github. So it seems that > Iceberg's FETCH did the right thing updating the remote. But the disk > working directory should have just fast-forwarded rather than merging. > > Now seeing both these commits... > * Merge with ref/remotes/origin/master > * Updated README > in the one [New commits to be imported] seems to be mixing results > from the working repo and the remote repo in a way that makes it hard > to guess the consequence of any next action here. > > I do see a <Merge and load> option when I right-click on one of those > commits. > Perhaps the "load" means to load from the disk working directory into > the Image(?) but its a bit hidden compared to the <Fetch> and <Pull> > that are buttons. > It seems dangerous to take that action right now, since I guess the > Image would diverge from the disk working directory. > > > FIXING... > > What I ended up doing was remove the "merge commit" from the disk > working directory > $ git reset --hard HEAD^ > > then opened a new Iceberg which for [Updates] only showed only the > single commit "Updated README" fetched into the remote repo. Good. > I right-clicked on that and did <Merge and load> which correctly > fast-forwarded the disk working directory... > $ git log > commit 587bed95c4b8fb3986c9962c9206405c81c99e3d > Author: Ben Coman <github.com(a)ben.coman.com.au> > Date: Thu Feb 8 11:54:20 2018 +0800 > Updated README > > commit c818e9adebeb6be001b202aa48da009be97920eb > Author: Ben Coman <btc(a)openInWorld.com> > Date: Thu Feb 8 11:42:57 2018 +0800 > Update class comment. > > commit 6f2df89b219c56530412252ace96bc95eb78373a > Author: Ben Coman <btc(a)openInWorld.com> > Date: Thu Feb 8 11:37:01 2018 +0800 > First Pharo code > > commit 52ab6ac696760a60fe56af57e45f2e2ceaaae35e > Author: Ben Coman <btc(a)openInWorld.com> > Date: Thu Feb 8 11:31:28 2018 +0800 > first commit > > However the same "Updated README" commit still shows in [New commits > to be imported] tab, but now its right-click menu item now shows only > <Load> rather than <Merge and load>. So it seem to correctly identify > the disk working directory is up to date but clicking on <Load> > doesn't change anything. Perhaps because there is no Pharo code to > load? Since only the README outside the "src" directory changed? > > Moving to the [Push] tab, this shows the four commits seen in the last > `git log` > This is confusing since I'd expect this to be empty since... > $ git log > /tmp/x1 > $ git log traadh/master > /tmp/x2 > $ diff /tmp/x1 /tmp/x2 > is empty > > Luckily clicking <Publish all> cleared out this list > with no impact on github network graph > https://github.com/Traadh/cloudflareun/network > > > SUMMARY > In the end I seem to got done what I needed. I'm enjoying Iceberg > more and more as I rub off the rough edges my understanding it. > Hopefully my report will help smooth things for others. > > My only remaining niggle is not being able to get rid of this "1 incoming", > but maybe that will disappear when I've got a code update to upload. > What version of Pharo/Icerberg are you using? There is a couple of glitches/bugs in iceberg 0.6.x regarding merges. - it ignores a commit when a commit only has changes in non smalltalk code (e.g., your README file) - it creates an extra merge commit in many situations that are not necessary These two problems should be fixed in the latest development version, where we revised the merge algorithm. The pull should effectively fast-forward and the commit that only touches the README should be recognized. Now, I read a separate issue in your email: the pull button does not do the same than the "Merge and Load" button of the last commit. I think that should be fixed also, but I should check. We should sync with Esteban to see when we can integrate/merge this new version. > > cheers -ben > > P.S. It might be if the Iceberg [Remotes] could have a "Log" menu item > that worked like `git log`. > > P.P.S. I think more thought needs to be given to whether mixing > updates from both the remote and disk working directory in the one > pane is beneficial? > As an alternative, perhaps some side-scrolling GTInspector-like panes > Image <--> Working Directory <--> Remote <--> Server(github) > would better represent the git model. > Or maybe statically position those panes in one window with buttons on > directed lines showing which way and how far a commit moves when that > button is pushed. > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Feb. 12, 2018

Re: [Pharo-dev] what is <localMetaclassMethod>

by Thierry Goubier

Hi Hernan, 2018-02-12 7:48 GMT+01:00 HernÃ¡n Morales Durand <hernan.morales(a)gmail.com>: > Hi Eliot, > > One could say that a pragma is a message without a method? > > I think pragmas were never been integrated properly into the system > browser. We can browses pragmas with the PragmaCollection but what I > mean is a pragma-aware browser. See for example, there are some > pragmas where is easy to infer the meaning: <magritteDescription>, > <gtInspectorPresentationOrder:>, and others <eProperty> where is not > so clear. So even if we take <gtInspectorPresentationOrder:> is not > easy with the current tools to find of which parameters makes sense. I > always missed something like the annotation pane plugin or the quality > assistant plugin in Nautilus, but for pragmas. What Eliot is pointing out, is that integration is very easy to do as long as you implement it the way Eliot describes it: you see a pragma, you select it, search for implementors, and, voilÃ , you know what the pragma is for and how it is used (and you may even get a comment for the parameters). Now, you can try to do that in Pharo, and, of course that doesn't work: I can select the pragma <gtInspectorPresentationOrder: 40>, search for implementors, and I get none. If I search for senders, among the few hundreds of senders I get into my pharo 6 image, and knowing that this should be inside the GT-Inspector-Core package, I find: #GTInspector class >>#extensionsPragma Now, following senders of #extensionsPragma, I find about a dozen senders (because there are multiple implementors of #extensionsPragma, probably). One of the senders is probably the key: ProtoObject>>#gtInspectorPresentationsIn:inContext: And the use of #allNamed:from:to:sortedUsing: should give you a clue about the argument (because, yes there is no comment about the argument... or even if the pragma should have one...). > This could be an excellent opportunity for Calypso to see how pragmas > can be exploited in the way you describe. As I said above, if used like Eliot describes, then it could be done just by searching implementors of the pragma symbol. Now, implemented as it is in Pharo, I suspect it will be hard to do even for Calypso. Regards, Thierry > Thanks for the kind explanation. > > Cheers, > > HernÃ¡n > > > 2018-02-12 1:09 GMT-03:00 Eliot Miranda <eliot.miranda(a)gmail.com>: >> Hi Hernan, >> >> >> >> >> _,,,^..^,,,_ (phone) >>> On Feb 11, 2018, at 10:47 AM, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: >>> >>> I don't know, but how you you find documentation about specific pragmas? >> >> The best way is to ensure the pragma has at least one implementation, i.e. there is at least one method in the system that has the same signature as the pragma. This implementation should document the pragma, but even better it should be the method that extracts information from the pragma. >> >> An example will help. Imagine a pragma that specifies a method belongs on some menu. The method containing the pragma is intended to be an action of the menu, do that when the menu item is selected, the method containing the pragma will b executed. The pragma defines the menu the method belongs to, where in the method, the string to appear in the menu, the hot key for the menu item, etc. >> >> If the pragma is implemented by a menu builder then >> - yes, certainly the pragma can be documented in the m by builder's implementation, but also >> - the menu can be built by performing the pragma by the menu builder >> >> This was my intent when Steve Dahl and I invented pragmas, that there would always be implementations of the pragma in classes that were designed to extract the information from the pragma and add the method containing the pragma to whatever structure the pragma was intended to facilitate updating (menus, inspectors, exported apis, etc). So the most powerful way of use my pragmas is via a visitor pattern: >> >> When a method with a particular pragma is added or removed, the class containing the method triggers some action. This action collects all the relevant pragma methods in the class hierarchy, creates some builder object, and has the builder perform each method containing a relevant pragma. >> >> Using pragmas as arbitrary labels is fine, bug doesn't exploit the fact that pragmas are messages, and that hence one can do senders and implementors /and/ perform them. >> >> HTH >> >>> >>> HernÃ¡n >>> >>> >>> 2018-02-11 14:48 GMT-03:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >>>> Hi >>>> >>>> what is this pragma in metaclass method? >>>> >>>> Stef >>>> >>> >> >

Feb. 12, 2018

Re: [Pharo-dev] Cleaning up... baseClass, instanceSide, theNonMetaclass

by Guillermo Polito

In my code I use to use instanceSide and classSide. don't know why. Maybe they are clearer to me? On Sun, Feb 11, 2018 at 8:59 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > 2018-02-11 18:14 GMT+01:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > >> Hi >> >> We already got this discussion and I plan to address it. >> Now I discovered that in addition to instanceSide and theNonMetaclass we >> have >> >> - classClass and baseClass >> - theMetaclass and theNonMetaclass >> - instanceSide and classSide >> >> https://pharo.fogbugz.com/f/cases/20941/deprecate-theMetacla >> ss-and-the-theNonMeta >> >> Even if instanceSide and classSide come from UI concerns I think that >> there are much >> better than the others. >> > > + 100 > > >> >> So have you any concerns and prefer one of the other couples? Because >> we should stop >> accumulate cruft in the system. We do not need three ways to do the same. >> >> Stef >> >> > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Feb. 12, 2018

[Pharo 7.0-dev] Build #530: 21314 Remove unnecessary "self run:" in IntervalTest and IdentityBagTest

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #530 was: SUCCESS. The Pull Request #842 was integrated: "21314 Remove unnecessary "self run:" in IntervalTest and IdentityBagTest" Pull request url: https://github.com/pharo-project/pharo/pull/842 Issue Url: https://pharo.fogbugz.com/f/cases/21314 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 12, 2018

[Pharo 7.0-dev] Build #529: 21289 Remove unnecessary "self run:" in BasicBehaviorClassMetaclassTest

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #529 was: SUCCESS. The Pull Request #866 was integrated: "21289 Remove unnecessary "self run:" in BasicBehaviorClassMetaclassTest" Pull request url: https://github.com/pharo-project/pharo/pull/866 Issue Url: https://pharo.fogbugz.com/f/cases/21289 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 12, 2018

Esteban's ChangeLog week of 5 February 2018

by estebanlm＠gmail.com

Hello! This is my weekly ChangeLog, from 5 February 2018 to 11 February 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=5/2/2018&to=11/2/2018 ChangeLog ========= 6 February 2018: ---------------- * ... and packaging should be [restored](https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/214) too. Which means latest vm versions are latest builds from OSVM: === 64bit * [http://files.pharo.org/get-files/70/pharo64-mac-latest.zip](http://files.ph… * [http://files.pharo.org/get-files/70/pharo64-linux-threaded-latest.zip](http… * [http://files.pharo.org/get-files/70/pharo64-linux-latest.zip](http://files.… * [http://files.pharo.org/get-files/70/pharo64-win-latest.zip](http://files.ph… === 32bit * [http://files.pharo.org/get-files/70/pharo-win-latest.zip](http://files.phar… * [http://files.pharo.org/get-files/70/pharo-linux-threaded-latest.zip](http:/… * [http://files.pharo.org/get-files/70/pharo-linux-latest.zip](http://files.ph… * [http://files.pharo.org/get-files/70/pharo-mac-latest.zip](http://files.phar… === Hints * MacOS VMs now are signed! This should fix a lot of problems we had before. * Please take note that latest win64 build lacks all library dependencies, and many things will not work (working on that) Thanks to [Fabio](https://github.com/fniephaus) to help me put all the pieces together. * Certificates should work now, and we can have a [signed VM](https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/214). * yesterday with Fabio we worked on fix an upload of pharo-vm that was failing: * [https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/160](https://githu… 5 February 2018: ---------------- * I released a patch for iceberg: * [iceberg 0.6.7](https://github.com/pharo-vcs/iceberg/releases/tag/v0.6.7) * [libgit 1.0.5](https://github.com/pharo-vcs/libgit2-pharo-bindings/releases/tag/v1.… * [tonel 1.0.6](https://github.com/pharo-vcs/tonel/releases/tag/v1.0.6) this is a maintenance version that fixes a couple of bugs and cleans a bit, but big changes will come next release (0.7) * I published new versions of the certifictes to get a signed mac VM. In theory, this time it should work :) cheers! Esteban

Feb. 12, 2018

Re: [Pharo-dev] what is <localMetaclassMethod>

by HernÃ¡n Morales Durand

Hi Eliot, One could say that a pragma is a message without a method? I think pragmas were never been integrated properly into the system browser. We can browses pragmas with the PragmaCollection but what I mean is a pragma-aware browser. See for example, there are some pragmas where is easy to infer the meaning: <magritteDescription>, <gtInspectorPresentationOrder:>, and others <eProperty> where is not so clear. So even if we take <gtInspectorPresentationOrder:> is not easy with the current tools to find of which parameters makes sense. I always missed something like the annotation pane plugin or the quality assistant plugin in Nautilus, but for pragmas. This could be an excellent opportunity for Calypso to see how pragmas can be exploited in the way you describe. Thanks for the kind explanation. Cheers, HernÃ¡n 2018-02-12 1:09 GMT-03:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > Hi Hernan, > > > > > _,,,^..^,,,_ (phone) >> On Feb 11, 2018, at 10:47 AM, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: >> >> I don't know, but how you you find documentation about specific pragmas? > > The best way is to ensure the pragma has at least one implementation, i.e. there is at least one method in the system that has the same signature as the pragma. This implementation should document the pragma, but even better it should be the method that extracts information from the pragma. > > An example will help. Imagine a pragma that specifies a method belongs on some menu. The method containing the pragma is intended to be an action of the menu, do that when the menu item is selected, the method containing the pragma will b executed. The pragma defines the menu the method belongs to, where in the method, the string to appear in the menu, the hot key for the menu item, etc. > > If the pragma is implemented by a menu builder then > - yes, certainly the pragma can be documented in the m by builder's implementation, but also > - the menu can be built by performing the pragma by the menu builder > > This was my intent when Steve Dahl and I invented pragmas, that there would always be implementations of the pragma in classes that were designed to extract the information from the pragma and add the method containing the pragma to whatever structure the pragma was intended to facilitate updating (menus, inspectors, exported apis, etc). So the most powerful way of use my pragmas is via a visitor pattern: > > When a method with a particular pragma is added or removed, the class containing the method triggers some action. This action collects all the relevant pragma methods in the class hierarchy, creates some builder object, and has the builder perform each method containing a relevant pragma. > > Using pragmas as arbitrary labels is fine, bug doesn't exploit the fact that pragmas are messages, and that hence one can do senders and implementors /and/ perform them. > > HTH > >> >> HernÃ¡n >> >> >> 2018-02-11 14:48 GMT-03:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >>> Hi >>> >>> what is this pragma in metaclass method? >>> >>> Stef >>> >> >

Feb. 12, 2018

Re: [Pharo-dev] what is <localMetaclassMethod>

by Eliot Miranda

Hi Hernan, _,,,^..^,,,_ (phone) > On Feb 11, 2018, at 10:47 AM, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > I don't know, but how you you find documentation about specific pragmas? The best way is to ensure the pragma has at least one implementation, i.e. there is at least one method in the system that has the same signature as the pragma. This implementation should document the pragma, but even better it should be the method that extracts information from the pragma. An example will help. Imagine a pragma that specifies a method belongs on some menu. The method containing the pragma is intended to be an action of the menu, do that when the menu item is selected, the method containing the pragma will b executed. The pragma defines the menu the method belongs to, where in the method, the string to appear in the menu, the hot key for the menu item, etc. If the pragma is implemented by a menu builder then - yes, certainly the pragma can be documented in the m by builder's implementation, but also - the menu can be built by performing the pragma by the menu builder This was my intent when Steve Dahl and I invented pragmas, that there would always be implementations of the pragma in classes that were designed to extract the information from the pragma and add the method containing the pragma to whatever structure the pragma was intended to facilitate updating (menus, inspectors, exported apis, etc). So the most powerful way of use my pragmas is via a visitor pattern: When a method with a particular pragma is added or removed, the class containing the method triggers some action. This action collects all the relevant pragma methods in the class hierarchy, creates some builder object, and has the builder perform each method containing a relevant pragma. Using pragmas as arbitrary labels is fine, bug doesn't exploit the fact that pragmas are messages, and that hence one can do senders and implementors /and/ perform them. HTH > > HernÃ¡n > > > 2018-02-11 14:48 GMT-03:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >> Hi >> >> what is this pragma in metaclass method? >> >> Stef >> >

Feb. 12, 2018