November 2014 - Pharo-users

Memoization Question

by Torsten Bergmann

Werner Kassens wrote: >Hi, >now this a nice idea, especially the memoizedUsing:cache idea. i would >really appreciate it, if that would be MIT licenced. >werner It already is, thanks to the permission of author John Cromartie who answered us today. Both methods are in a slice already: Details in https://pharo.fogbugz.com/f/cases/14458 Thx T.

Nov. 11, 2014

Re: [Pharo-users] Memoization Question

by Werner Kassens

Hi, now this a nice idea, especially the memoizedUsing:cache idea. i would really appreciate it, if that would be MIT licenced. werner

Nov. 11, 2014

Re: [Pharo-users] Is there a way to store workspace 'gists' in Pharo?

by Andy Burnett

Stef said: << I usually create a method and a class. because script do not compose well. >> á§ > > Thanks, that sounds interesting. And, just for clarity, do you mean that you create a single class e.g. MyGists and then create methods for each of your useful snippets? Or, is there a benefit in creating a class per gist? Cheers

Nov. 11, 2014

Re: [Pharo-users] Is there a way to store workspace 'gists' in Pharo?

by Pierce Ng

On Tue, Nov 11, 2014 at 04:37:03PM +0100, stepharo wrote: > I usually create a method and a class. > because script do not compose well. +1 although I don't practise this well. I use ScriptManager but when my images proliferate it becomes messy to manage the scripts across images. Pierce

Nov. 11, 2014

Re: [Pharo-users] Memoization Question

by Sven Van Caekenberghe

This is cool indeed. I find an unlimited cache a bit coarse, would not really work in practice. What about memoizedUsing: cache ^ [ :x | cache at: x ifAbsentPut: [ self value: x ] ] then you could pass in a tuned LRUCache instance, among others. Sven > On 11 Nov 2014, at 16:24, Torsten Bergmann <astares(a)gmx.de> wrote: > > Phil wrote: >> thanks for the pointer. >> Now, how do I use that? > > > First: create a method BlockClosure>>#memoized in your Pharo image (see https://gist.github.com/jcromartie/2705526) > > memoized > "returns memoized version of an unary function" > | cache | > cache := Dictionary new. > ^ [ :x | cache at: x ifAbsentPut: [ self value: x ] ]! > > > So the idea of #memoized is to return a new "outer" block who evaluates the original block only when the computation > of the inner block was not yet done/the result of the inner evaluation is not yet cached. > > > As you see from the comment it works for "unary functions" which would mean it works > for "one argument blocks". Simple example: > > |square memo | > square:= [:x | Transcript show: 'Processing'. x * x]. > memo := square memoized. > memo value: 2. > memo value: 3. > memo value: 2. > > The Transcript only shows "Processing" two times instead of three times, so only for the first two #value: calls > we have to calculate x * x. > > For the last evaluation on the memo block (with argument 2 again) the result is already known from the cache, > so the square block is not evaluated again. Instead the cached result could be returned which could be faster > than doing the computation again. > > x*x is only an example - this "memoization" can usually speed up when a block is costly (performancewise) and > is often called with the same arguments. A precondition (for this caching) is that the block evalutes the > same way/returns the same result for the same input argument. > > > You also try the two prepared workspaces in Pharo: > > Non-memoized version: http://ws.stfx.eu/5ZE87XSFL9IH > Memoized Version: http://ws.stfx.eu/QLQLSLT7PZ4C > > Hope this makes it more clear. This simple example is a nice performance trick and shows again the power > of Smalltalk and block closures. > > Dont know about the license - but we could ask author John Cromartie for MIT license to include this simple > method into the standard image. I will try to contact him. > > Bye > T. >

Nov. 11, 2014

Re: [Pharo-users] Is there a way to store workspace 'gists' in Pharo?

by stepharo

Hi andy I usually create a method and a class. because script do not compose well. Stef > From time to time I write a workspace script that I would like to > keep. Obviously, I could save them to a file, but I was wondering if > there was a way of saving them in the image, and browsing them in some > friendly way? > > Cheers > Andy > á§

Nov. 11, 2014

Re: [Pharo-users] Memoization Question

by Torsten Bergmann

Phil wrote: >thanks for the pointer. >Now, how do I use that? First: create a method BlockClosure>>#memoized in your Pharo image (see https://gist.github.com/jcromartie/2705526) memoized "returns memoized version of an unary function" | cache | cache := Dictionary new. ^ [ :x | cache at: x ifAbsentPut: [ self value: x ] ]! So the idea of #memoized is to return a new "outer" block who evaluates the original block only when the computation of the inner block was not yet done/the result of the inner evaluation is not yet cached. As you see from the comment it works for "unary functions" which would mean it works for "one argument blocks". Simple example: |square memo | square:= [:x | Transcript show: 'Processing'. x * x]. memo := square memoized. memo value: 2. memo value: 3. memo value: 2. The Transcript only shows "Processing" two times instead of three times, so only for the first two #value: calls we have to calculate x * x. For the last evaluation on the memo block (with argument 2 again) the result is already known from the cache, so the square block is not evaluated again. Instead the cached result could be returned which could be faster than doing the computation again. x*x is only an example - this "memoization" can usually speed up when a block is costly (performancewise) and is often called with the same arguments. A precondition (for this caching) is that the block evalutes the same way/returns the same result for the same input argument. You also try the two prepared workspaces in Pharo: Non-memoized version: http://ws.stfx.eu/5ZE87XSFL9IH Memoized Version: http://ws.stfx.eu/QLQLSLT7PZ4C Hope this makes it more clear. This simple example is a nice performance trick and shows again the power of Smalltalk and block closures. Dont know about the license - but we could ask author John Cromartie for MIT license to include this simple method into the standard image. I will try to contact him. Bye T.

Nov. 11, 2014

Memoization Question

by Torsten Bergmann

Nov. 10, 2014

Re: [Pharo-users] Ploting all history of the commits in a Monticello repository

by Stephan Eggermont

You might get some inspiration by taking a look at http://smalltalkhub.com/#!/~StephanEggermont/DeprecationFinder Stephan

Nov. 10, 2014

Ploting all history of the commits in a Monticello repository

by Offray Vladimir Luna CÃ¡rdenas

Hi, I don't know if the terminology is the proper one. Anyway I'm trying to plot a "time line" of the history of a project which is stored on [1] and [2] (after rebranding) and also of the commits to documentation on [3] using Pharo/Roassal. [1] http://smalltalkhub.com/#!/~Offray/Ubakye/ [2] http://smalltalkhub.com/#!/~Offray/Grafoscopio/ [3] http://mutabit.com/deltas/repos.fossil/grafoscopio/timeline?n=200 Given I don't know any API of the sites, I thought it would be easier by scraping the data on the web pages and the using it into Roassal, but after testing some solutions on python, I came back to pharo to see if I can made everything on it, including the data collection. For [1] and [2] I think that is possible to send a message to Monticello to show all commits of a specific package (like it actually does from the UI) and export them with the information about date of commit for all commits. For [3] I'm thinking in using some combination of Zinc with Soup[4] despite of the lack of tutorials. [4] http://www.squeaksource.com/@Y-xGMSBYZmiWQToh/GJDsBRqL So here are my questions: - There is any way to say to Monticello to export all commits dates and times for a specific package? - There is any advised scraping strategy for getting the same information from the web page at [3]? The plot I would like to do is similar to the one of the ebola example at [5], but using high as number of commits and x axis as dates. [5] https://dl.dropboxusercontent.com/u/31543901/AgileVisualization/QuickStart/… Any help is welcomed, as always. Cheers, Offray

Nov. 10, 2014

Re: [Pharo-users] question on syntax "negate numbers"

by Werner Kassens

dont know but <g> let me try yet another attempt at rephrasing this. suppose you ask an intermediate beginner how 5--4 would be parsed, as: a) 5 - -4 b) 5 -- 4 perhaps he does not need to look up the chapter in the pharobook and will choose b). but if he looks into the pharobook he will read under "Binary messages": "Note that ââ is not allowed for parsing reasons" (i just checked the latest version) now honestly, dont you think that a) is a serious contender? that is all i wanted to say. werner

Nov. 10, 2014

Re: [Pharo-users] question on syntax "negate numbers"

by Thierry Goubier

2014-11-10 15:57 GMT+01:00 Werner Kassens <wkassens(a)libello.com>: > Let me restate what i meant: if you enter 5--4 in squeak for example, the > parser asks you whether you meant 5 - -4 or 5 -- 4. Oh, ok. And what happens if you are not in an interactive mode (like when you are filing-in code) ? Thierry > > werner > > > On 11/10/2014 03:28 PM, Werner Kassens wrote: > >> Of course. i was talking about x -- y not x - - y. >> werner >> >> On 11/10/2014 03:17 PM, Thierry Goubier wrote: >> >>> I believe that x - - y would give you an error. >>> >>> 4 - - 5 in parsing is a different beast, because you consider - 5 as a >>> single token. >>> >> >> >> >> >

Nov. 10, 2014

Re: [Pharo-users] Is there a way to store workspace 'gists' in Pharo?

by Andy Burnett

á§ Doru said <<< If you work with Pharo 4, they should already be saved in a play-cache folder. >> Great, I shall go and experiment. Cheers Andy

Nov. 10, 2014

Re: [Pharo-users] AST #copy behavior

by Mark Rizun

> > >> The AST generated by SmaCC has a postCopy in the same way that you > describe, so I'd say this is OK. > > That's good > Just be precise about what you copy and what you don't copy. Can you say > what will be copied and what won't? > For instance, in RBMethodNode I want to copy replacements inst var. Another example: for RBReturnNode - return and value inst vars.

Nov. 10, 2014

Re: [Pharo-users] Is there a way to store workspace 'gists' in Pharo?

by Peter UhnÃ¡k

There is also ScriptManager http://smalltalkhub.com/#!/~TorstenBergmann/ScriptManager but I do not know if it works with GTPlaygrounds and it seems to have some issues with Morphic? Peter On Mon, Nov 10, 2014 at 3:56 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > If you work with Pharo 4, they should already be saved in a play-cache > folder. > > Cheers, > Doru > > > On Mon, Nov 10, 2014 at 3:55 PM, Andy Burnett < > andy.burnett(a)knowinnovation.com> wrote: > >> From time to time I write a workspace script that I would like to keep. >> Obviously, I could save them to a file, but I was wondering if there was a >> way of saving them in the image, and browsing them in some friendly way? >> >> Cheers >> Andy >> á§ >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Nov. 10, 2014

Webdoc: status?

by phil＠highoctane.be

I'd like to use WebDoc for generating my project code doc; I see that https://ci.inria.fr/pharo-contribution/job/WebDoc/ is pretty much red for a long time. Started by timer Building remotely on pharo-contribution-win7.ci.inria.fr <https://ci.inria.fr/pharo-contribution/computer/pharo-contribution-win7.ci.…> (win7 32 win) in workspace C:\builds\workspace\WebDoc Deleting project workspace... done Triggering 30,development,vm <https://ci.inria.fr/pharo-contribution/job/WebDoc/PHARO=30,VERSION=developm…>30,development,vm <https://ci.inria.fr/pharo-contribution/job/WebDoc/PHARO=30,VERSION=developm…> completed with result FAILURE Deleting matrix project workspace... Skipped based on build state FAILURE Finished: FAILURE But the green one isn't more indicative of success... What's the status? Is it used by someone? I tried the config and it crashed; github-camillobruniPPMarkdown184.... does not exit. :-( The catalog says: https://ci.inria.fr/pharo-contribution/job/PharoProjectCatalog/HTML_Report/ So, - I cloned Esteban's github repo (git(a)github.com=estebanlm/pharo-webdoc.git - git submodule init update --init Loaded by hand the packages in the submodule (petitmarkdown) Loaded the WebDoc package (the SimpleWebDoc doesn't load, even if I have Seaside in my image). In a workspace: (WebDocExporter packages: RPackageOrganizer default packages) exportTo: './doc' asFileReference. Which started to generate html files in doc/ nicely but choked while exporting FFITestLibrary Ideas why it fails? Known issue? TIA Phil

Nov. 10, 2014

Re: [Pharo-users] question on syntax "negate numbers"

by Werner Kassens

Let me restate what i meant: if you enter 5--4 in squeak for example, the parser asks you whether you meant 5 - -4 or 5 -- 4. werner On 11/10/2014 03:28 PM, Werner Kassens wrote: > Of course. i was talking about x -- y not x - - y. > werner > > On 11/10/2014 03:17 PM, Thierry Goubier wrote: >> I believe that x - - y would give you an error. >> >> 4 - - 5 in parsing is a different beast, because you consider - 5 as a >> single token. > > >

Nov. 10, 2014

Re: [Pharo-users] Is there a way to store workspace 'gists' in Pharo?

by Tudor Girba

If you work with Pharo 4, they should already be saved in a play-cache folder. Cheers, Doru On Mon, Nov 10, 2014 at 3:55 PM, Andy Burnett < andy.burnett(a)knowinnovation.com> wrote: > From time to time I write a workspace script that I would like to keep. > Obviously, I could save them to a file, but I was wondering if there was a > way of saving them in the image, and browsing them in some friendly way? > > Cheers > Andy > á§ > -- www.tudorgirba.com "Every thing has its own flow"

Nov. 10, 2014

Is there a way to store workspace 'gists' in Pharo?

by Andy Burnett

>From time to time I write a workspace script that I would like to keep. Obviously, I could save them to a file, but I was wondering if there was a way of saving them in the image, and browsing them in some friendly way? Cheers Andy á§

Nov. 10, 2014

Re: [Pharo-users] AST #copy behavior

by Thierry Goubier

2014-11-10 14:38 GMT+01:00 Mark Rizun <mrizun(a)gmail.com>: > Hi guys! > > I'm using AST really often, and recently stumbled on problem with copying > an > AST. > It doesn't copy stuff related to computing sourceInterval of AST, and I > need > it to copy:) > > I know there are #deepCopy and #veryDeepCopy, but they are too heavy > methods > for AST, especially in my case, as I need to copy AST all the time. > > Earlier, I discussed this problem with Marcus Denker. He suggested to fix > #copy of AST (to be more accurate #postCopy). > If I want to copy stuff related to sourceInterval, I would have to > implement > #postCopy for each RBNode... differently. > > RBProgramNode>>#postCopy > super postCopy. > properties := properties copy > > So for each RBNode... it will be like: > > RBNode...>>#postCopy > super postCopy. > "here some different code each time" > > I'm just interested: What do you think about it? > The AST generated by SmaCC has a postCopy in the same way that you describe, so I'd say this is OK. Just be precise about what you copy and what you don't copy. Can you say what will be copied and what won't? Thierry > > Thanks, > Mark > > > > -- > View this message in context: > http://forum.world.st/AST-copy-behavior-tp4789447.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Nov. 10, 2014

Re: [Pharo-users] question on syntax "negate numbers"

by Werner Kassens

Of course. i was talking about x -- y not x - - y. werner On 11/10/2014 03:17 PM, Thierry Goubier wrote: > I believe that x - - y would give you an error. > > 4 - - 5 in parsing is a different beast, because you consider - 5 as a > single token.

Nov. 10, 2014

Re: [Pharo-users] question on syntax "negate numbers"

by Thierry Goubier

I believe that x - - y would give you an error. 4 - - 5 in parsing is a different beast, because you consider - 5 as a single token. Thierry 2014-11-10 12:36 GMT+01:00 Henrik Johansen <henrik.s.johansen(a)veloxit.no>: > In VisualWorks: > 3 @ *Argument expected ->*- 5 > > I guess what one expects is a matter of habit, personally I'd expect x - - > y to yield a parsing error. > > Cheers, > Henry > > On 10 Nov 2014, at 12:06 , PBKResearch <peter(a)pbkresearch.co.uk> wrote: > > I have tried this on my latest Dolphin (Pro 6.1 Beta 2): > 3 @ -5 is accepted and interpreted correctly. > 3 @ - 5 is rejected with message: 'Error - incorrect expression start'; > the caret is pointing at the - sign. > So the Opal behaviour does not mirror that of Dolphin. > > Hope this helps > > Peter Kenny > > > *From:* Pharo-users [mailto:pharo-users-bounces@lists.pharo.org > <pharo-users-bounces(a)lists.pharo.org>] *On Behalf Of *Thierry Goubier > > 2014-11-10 8:47 GMT+01:00 Henrik Johansen <henrik.s.johansen(a)veloxit.no>: > > 3 @ -5 is not a problem, and accepted by both. > 3 @ - <space> 5 is what I object to (and Opal allows) > > > > RBParser allows this one even if old Compiler dissallows it (i.e. in Pharo > 2). > > I haven't tracked if Opal follows the RBParser on that or if this is the > reverse (Opal pushed changes on RBParser). I suspect all things RB in Pharo > (and Squeak?) are a port from the Dolphin version of RB, which means this > is allowed in quite a few other smalltalks (Dolphin?, VW?). > > I haven't checked if the SmaCC Smalltalk parser accept that. > Note: 4 - 5 in RBParser does what you would expect. 4 - - 5 as well. > > > 3 @-5 and/or 3 @- 5 is (rightly) disallowed by both. > > > > That one is easier and expected. > My position would be twofold: > - RBParser is, IMHO, a good parser and I would follow its interpretation. > That Opal reuses it is a good point for me. > - As a programming language designer (and parser implementor), accepting - > 5 is user friendly, but a bit too contextual in the lexer to be nice to > implement. > > Thierry > > > > Cheers, > Henry > > >

Nov. 10, 2014

AST #copy behavior

by Mark Rizun

Hi guys! I'm using AST really often, and recently stumbled on problem with copying an AST. It doesn't copy stuff related to computing sourceInterval of AST, and I need it to copy:) I know there are #deepCopy and #veryDeepCopy, but they are too heavy methods for AST, especially in my case, as I need to copy AST all the time. Earlier, I discussed this problem with Marcus Denker. He suggested to fix #copy of AST (to be more accurate #postCopy). If I want to copy stuff related to sourceInterval, I would have to implement #postCopy for each RBNode... differently. RBProgramNode>>#postCopy super postCopy. properties := properties copy So for each RBNode... it will be like: RBNode...>>#postCopy super postCopy. "here some different code each time" I'm just interested: What do you think about it? Thanks, Mark -- View this message in context: http://forum.world.st/AST-copy-behavior-tp4789447.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Nov. 10, 2014

Re: [Pharo-users] Anyone having a Rserve client?

by Thierry Goubier

2014-11-10 12:07 GMT+01:00 phil(a)highoctane.be <phil(a)highoctane.be>: > > We are using UCS here. There are nice babies in that lineup: > > > http://www.cisco.com/c/en/us/products/servers-unified-computing/ucs-c420-m3… > Yes, This is this class of stuff our user has. Thierry > > > Phil > >> >> >> Thierry >> >> >

Nov. 10, 2014

Re: [Pharo-users] question on syntax "negate numbers"

by Werner Kassens

>3 @ - <space> 5 is what I object to (and Opal allows) with this i have no problems, it follows simple obvious rules as long as one knows that #@ cant be an unary operator. >is 4 - 5 two literals, or is it two literals separated by the - operator ? but then there is no situation in which the - operator can really operate and where a sequence of literals is at the same time possible. ok there is #(4 - 5), but in this case the operator cant operate and first the #()-thing is parsed and then its elements. what has not been mentioned is: 4 -- 5, which in a certain way was (?) problematic: my (old) pharobook (p.64) says: "Note that ââ is not allowed for parsing reasons". in this case it should be seen as 4 - -5 and one needed to keep this special case in his mind, but i had no problems defining a #--, which simplifies everything: if there is no special case, then -- has to be parsed as one binary operator. and i only have an old pharobook, a newer one perhaps (?) doesnt state this. all this just from my simple user perspective of course, but i guess the question was not posed without reason in Pharo-Users. and this simple user prefers freedom over paternalism anyday. werner

Nov. 10, 2014