June 2015 - Pharo-dev - lists.pharo.org

Pratt Parsers for PetitParser

by Camille

Hello Pharoers and Moosers, I did a Pratt parser extension for PetitParser. A Pratt parser (a.k.a top-down operator precedence parser) handles left-recursion and operator precedence. It handles grouping, prefix, postfix, infix (right- or left-associative) and "multifixâ operators (e.g. "if ... then ... else ...", "... ? ... : ...", Smalltalk keyword messages). Normally Pratt Parsing needs a tokenization phase but here tokenization is done on the fly with other PP parsers. Apart from tokenization, no backtracking is needed so parsing is quite fast (approximatively 2 times faster than PPExpressionParser). Here is an exemple of a calculator: parser := PPPrattParser new. "Numbers" parser terminal: #digit asParser plus do: [ :token | token inputValue asNumber ]. parser skip: #space asParser plus. "Parentheses" parser groupLeft: $( asParser right: $) asParser. "Addition, substraction, multiplication, division: all left infix, * and / have higher precedence than + and -" parser leftInfix: $+ asParser precedence: 1 do: [ :left :op :right | left + right ]. parser leftInfix: $- asParser precedence: 1 do: [ :left :op :right | left - right ]. parser leftInfix: $* asParser precedence: 2 do: [ :left :op :right | left * right ]. parser leftInfix: $/ asParser precedence: 2 do: [ :left :op :right | left / right ]. "Power: right infix with higher precedence than multiplication and division" parser rightInfix: $^ asParser precedence: 3 do: [ :left :op :right | left raisedTo: right ]. "Unary minus: prefix with highest precedence" parser prefix: $- asParser precedence: 4 do: [ :op :right | right negated ]. parser parse: '2*3 + 4^(1/2)*3' ----> 12 To try it: Gofer it smalltalkhubUser: 'CamilleTeruel' project: 'PetitPratt'; package: 'PetitPratt'; load Note that it is in beta stage so it might still change drastically. @PP Devs: I had trouble with the PPContext furthestFailure that is taken into account instead of the failures I return, so I had to redefine #parseWithContext: to return the failures I want. The results given by furthestFailure were not very meaningful in my case (the same is true for PPExpressionParser btw). But I guess it was introduced because it gives good results in other cases. So would it be possible to change this behavior to let the parser decide if it returns the furthestFailure or the original failure? Cheers, Camille

June 10, 2015

[pharo-project/pharo-core] 2d03d7: 50102

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 2d03d702cccb68ca209646adc4d42be96900ab61 https://github.com/pharo-project/pharo-core/commit/2d03d702cccb68ca209646ad… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-06-10 (Wed, 10 Jun 2015) Changed paths: M Kernel.package/CompiledMethod.class/instance/accessing/originMethod.st M Keymapping-KeyCombinations.package/KMCommandModifier.class/instance/accessing/eventCode.st M Keymapping-KeyCombinations.package/KMCommandModifier.class/instance/matching/matchesEvent_.st R Keymapping-KeyCombinations.package/KMCommandModifier.class/instance/printing/symbol.st R Keymapping-KeyCombinations.package/KMCommandModifier.class/instance/private/delegatedModifier.st M Keymapping-KeyCombinations.package/KMKeyCombination.class/class/instance creation/fromKeyboardEvent_.st M Keymapping-KeyCombinations.package/KMMetaModifier.class/instance/accessing/eventCode.st A Keymapping-KeyCombinations.package/KMMetaModifier.class/instance/comparing/=.st A Keymapping-KeyCombinations.package/KMMetaModifier.class/instance/comparing/hash.st M Keymapping-KeyCombinations.package/KMMetaModifier.class/instance/matching/matchesEvent_.st A Keymapping-KeyCombinations.package/KMMetaModifier.class/instance/matching/matches_.st M Keymapping-KeyCombinations.package/KMModifiedKeyCombination.class/instance/matching/matchesEvent_.st M Keymapping-KeyCombinations.package/KMModifier.class/instance/comparing/hash.st M Keymapping-KeyCombinations.package/extension/MacOSPlatform/instance/defaultModifier.st M Keymapping-Tests.package/KMShortcutTest.class/instance/tests/testEventCodes.st A Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - reifications/testReifyGlobalValue.st A Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - reifications/testReifyTempValue.st A Reflectivity-Tests.package/ReflectivityExamples.class/instance/examples/exampleGlobalRead.st A Reflectivity.package/RFEReceiverReification.class/README.md A Reflectivity.package/RFEReceiverReification.class/class/plugin interface/key.st A Reflectivity.package/RFEReceiverReification.class/class/plugin interface/nodes.st A Reflectivity.package/RFEReceiverReification.class/definition.st A Reflectivity.package/RFEReceiverReification.class/instance/generate/genForRBMethodNode.st M Reflectivity.package/RFSemanticAnalyzer.class/instance/visiting/visitNode_.st M Reflectivity.package/RFSemanticAnalyzer.class/instance/visiting/visitVarWrite_.st M Reflectivity.package/RFValueReification.class/instance/generate/genForRBAssignmentNode.st M Reflectivity.package/RFValueReification.class/instance/generate/genForRBTempVariableNode.st M Reflectivity.package/RFValueReification.class/instance/generate/genForRBVariableNode.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50101.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50102.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50101.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50102.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A System-VMEvents.package/InputEventLog.class/README.md A System-VMEvents.package/InputEventLog.class/definition.st A System-VMEvents.package/InputEventLog.class/instance/accessing/filter_.st A System-VMEvents.package/InputEventLog.class/instance/events/handleEvent_.st Log Message: ----------- 50102 10803 Aliasing a method to a non-existent method breaks Browser https://pharo.fogbugz.com/f/cases/10803 15728 Meta support in keymapping https://pharo.fogbugz.com/f/cases/15728 15730 tests for #value (Global, Temp) and fix: allow tests to be run multiple times https://pharo.fogbugz.com/f/cases/15730 http://files.pharo.org/image/50/50102.zip

June 10, 2015

[pharo-project/pharo-core]

by GitHub

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

June 10, 2015

Detecting the context/producer of code change announcements

by Martin Dias

Hi everybody, I'm writing you to discuss about a new feature for Pharo. I would like to know your opinions and ideas. Thanks in advance. My point is that there are operations like "MC version load", "change set file in", "RB refactoring execution", or "class copy" that produce code change announcements (e.g. ClassAdded or MethodAdded), but subscribers can't know that. I mean, a subscriber that listens a ClassAdded can't know if it is product of a "high-level" operation, or if it was manually performed by the user in the Nautilus browser. I think Pharo should provide a way to detect this information, because it can be very useful. For example, I can tell you about a tool I work on: Epicea. Epicea logs code changes while developer works (like traditionally done with the .changes file), and the user can browse, undo and redo changes. Now, imagine that your vm crashed and then you want to recover "lost" changes... you don't want to see hundreds of changes produced by Monticello when loading packages: in this case, such changes are noise and make you waste time when selecting what to redo. In Epicea package I have a workaround for detecting some "high-level" operations, but Epicea would need support from Pharo for a nice implementation. Brainstorming on implementations. I think announcements are a good mechanism to implement this feature. A simple approach is to provide *begin* and *end* *announcements* (e.g. *MCVersionLoadBegin* and *MCVersionLoadEnd*). Then, somebody that subscribes to such announcements can have a stack or state machine to know the context where each code change announcement is produced. It would look like: MCVersionLoader >> load ... SystemAnnouncer uniqueInstance announce: (*MCVersionLoadBegin* versionName: ...). [ ... produce code changes ... ] *ensure:* [ SystemAnnouncer uniqueInstance announce: (*MCVersionLoadEnd* versionName: ...) ]. which may be re-written with a convenience method as: ... SystemAnnouncer uniqueInstance *announceBefore*: (MCVersionLoadBegin versionName: ...) *announceAfter*: (MCVersionLoadEnd versionName: ...) *do: *[ ... produce code changes ... ] but, going one step further, we could reify the concept of announcement *begin* and *end* like: ... *announcement := (MCVersionLoad versionName: ...).* SystemAnnouncer uniqueInstance announceBefore: (*AnnouncementBegin* of: announcement) announceAfter: (*AnnouncementEnd* of: announcement) do: [ ... produce code changes ... ] which could be re-written as: ... SystemAnnouncer uniqueInstance *announceBeforeAndAfter*: (MCVersionLoad versionName: ...) *do*: [ ... produce code changes ... ] I think any approach can work, but I'd love to have some feedback. Kind regards, MartÃn

June 10, 2015

Re: [Pharo-dev] Printing in transcript inside a loop

by phil＠highoctane.be

On Wed, Jun 10, 2015 at 11:56 AM, Matthieu Lacaton < matthieu.lacaton(a)gmail.com> wrote: > Hello, > > You need to fork it to be able to see the updates right away. > Or ask for the world to happen if the code is in the UI thread. World doOneCycle http://stackoverflow.com/questions/15372103/using-morphic-step-method-outsi… Phil > > An example : > > [ 1 to: 100 do: [ :i | > Transcript show: i asString. > (Delay forMilliseconds: 20) wait. > ] ] fork > > Cheers, > > Matthieu > > 2015-06-10 11:48 GMT+02:00 Sebastian Tleye <sebastian.tleye(a)gmail.com>: > >> Hi all, >> >> I want to print in the transcript from inside a loop, the problem I am >> seeing is that it does not print until the loop is finished. Is it a bug or >> do I have to configure something? >> >> This is a piece of code to exemplify it >> >> (1 to: 10000) do: [ :i | >> Transcript show: i asString. >> ] >> >> Thanks in advance >> >> By the way, I am using Pharo 3. >> >> -- >> SebastiÃ¡n Tleye >> > >

June 10, 2015

Re: [Pharo-dev] Comments in STON

by stepharo

This is in the entreprise book. I added a subsection on comments. May be I committed but forgot to push. Now I did it. Stef Le 9/6/15 21:50, Sven Van Caekenberghe a Ã©crit : > Where exactly can I find what you changed ? > I don't see any commit of you on github ... > >> On 09 Jun 2015, at 20:10, stepharo <stepharo(a)free.fr> wrote: >> >> >> >> Le 9/6/15 20:06, stepharo a Ã©crit : >>> I will update the STON chapter :) >> Done :) >> >>> >>> Le 8/6/15 23:39, Sven Van Caekenberghe a Ã©crit : >>>> I would do it like this: use a wrapping stream to skip comments. >>>> >>>> === >>>> Name: STON-Core-SvenVanCaekenberghe.59 >>>> Author: SvenVanCaekenberghe >>>> Time: 8 June 2015, 11:34:32.886167 pm >>>> UUID: 7ab942b5-9d1a-44c3-9d58-da29feb72380 >>>> Ancestors: STON-Core-SvenVanCaekenberghe.58 >>>> >>>> Add experimental STONCStyleCommentsSkipStream and tests >>>> === >>>> Name: STON-Tests-SvenVanCaekenberghe.54 >>>> Author: SvenVanCaekenberghe >>>> Time: 8 June 2015, 11:34:52.918771 pm >>>> UUID: 3dcb2c9c-6efe-4d62-bf36-3bbe91f09d08 >>>> Ancestors: STON-Tests-SvenVanCaekenberghe.53 >>>> >>>> Add experimental STONCStyleCommentsSkipStream and tests >>>> === >>>> >>>> Then you can do as follows: >>>> >>>> STON fromStream: (STONCStyleCommentsSkipStream on: 'Point[/* this is X*/ 1, /* this is Y*/ 2] // Nice huh ?' readStream). >>>> >>>> => 1@2 >>>> >>>> STON fromStream: (STONCStyleCommentsSkipStream on: '// Here is how you create a point: >>>> Point[ >>>> // this is X >>>> 1, >>>> // this is Y >>>> 2 ] >>>> // Nice huh ?' readStream). >>>> >>>> => 1@2 >>>> >>>> This helper class would be useable in other contexts too (like NeoJSON). >>>> >>>> The advantage is that it does not change the STON (or JSON) syntax itself, it just add some functionality for those who want it. >>>> >>>> What do you think ? >>>> >>>> Sven >>>> >>>> PS: this probably needs some more testing >>>> >>>>> On 08 Jun 2015, at 17:16, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>>> >>>>>> On 08 Jun 2015, at 17:03, Damien Cassou <damien.cassou(a)inria.fr> wrote: >>>>>> >>>>>> >>>>>> Sven Van Caekenberghe <sven(a)stfx.eu> writes: >>>>>> >>>>>>> I am not so sure we should add that. >>>>>>> >>>>>>> The JSON spec explicitly does not allow comments because of fear of abuse (that the comments would be used to add semantic meaning outside the spec). >>>>>> really? That's surprising. Comments in configuration files are very >>>>>> important. Even more when the configuration files are templates for new >>>>>> users. >>>>> I know some people are using STON in ways that I did not originally anticipate, that is of course cool, but writing configuration files was not the original goal. STON is a version of JSON that is closer to our object model. >>>>> >>>>> Like I said, I will think about it. >>>>> >>>>>> -- >>>>>> Damien Cassou >>>>>> http://damiencassou.seasidehosting.st >>>>>> >>>>>> "Success is the ability to go from one failure to another without >>>>>> losing enthusiasm." --Winston Churchill >>>> >>> >>> >> > >

June 10, 2015

Re: [Pharo-dev] [Reflectivity] progress on reifications

by Marcus Denker

> On 09 Jun 2015, at 15:23, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> On 09 Jun 2015, at 15:12, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> >>> On 09 Jun 2015, at 14:55, Francisco Garau <francisco.garau(a)gmail.com> wrote: >>> >>> Hi Marcus >>> >>> I'm sure this is great. Just a quick question on your example code: where is tag being defined? Is it an instance variable from ReflectiveMethodTest? >>> >> >> Yes, The test instance is put as the meta-object and we call #tagExec: there. This is just: >> >> tagExec: aTag >> tag := aTag. >> >> So we just call it with an argument, in this case the new value of the variable. >> >> This is in the image #testReifyNewValue. > > there is still an issue that one can not run this test twiceâ¦ I added it to the backlog: > > Fixed: https://pharo.fogbugz.com/f/cases/15730/t - tests for #value (Global, Temp) - fix for #value reification - fix: allow tests to be run multiple times - untested: add #receiver reification for message send Marcus

June 10, 2015

Re: [Pharo-dev] shortcut change in pharo 50075

by Sean P. DeNigris

Nicolai Hess wrote >> I like meta because there is no concrete "meta" key, so it's less >> confusing > Ok, I take this as a decision! Great :) ----- Cheers, Sean -- View this message in context: http://forum.world.st/shortcut-change-in-pharo-50075-tp4829460p4831396.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 10, 2015

Re: [Pharo-dev] Printing in transcript inside a loop

by Sebastian Tleye

Ah ok, thank you Mathieu! 2015-06-10 11:56 GMT+02:00 Matthieu Lacaton <matthieu.lacaton(a)gmail.com>: > Hello, > > You need to fork it to be able to see the updates right away. > > An example : > > [ 1 to: 100 do: [ :i | > Transcript show: i asString. > (Delay forMilliseconds: 20) wait. > ] ] fork > > Cheers, > > Matthieu > > 2015-06-10 11:48 GMT+02:00 Sebastian Tleye <sebastian.tleye(a)gmail.com>: > >> Hi all, >> >> I want to print in the transcript from inside a loop, the problem I am >> seeing is that it does not print until the loop is finished. Is it a bug or >> do I have to configure something? >> >> This is a piece of code to exemplify it >> >> (1 to: 10000) do: [ :i | >> Transcript show: i asString. >> ] >> >> Thanks in advance >> >> By the way, I am using Pharo 3. >> >> -- >> SebastiÃ¡n Tleye >> > > -- SebastiÃ¡n Tleye

June 10, 2015

Yet another Athens font thread

by Aliaksei Syrel

Hi I noticed that if I force use "Source Code Pro" as standard font for all elements in the image I never have problems with font rendering. In case of "Source Sans Pro" font is just not usable becasue of rendering bugs on mac, windows and linux(?). If "Lucida Sans Pro" is used - no bugs too. Because bug is reproducable on all platform - it's platform independent bug. Because it's reproducable only with one specific font - maybe it's not an athens issue but bug in font itself and if someone could change/update Source Sans Pro to a newly version or to a similar font the problem will be solved? Cheers, Alex

June 10, 2015