September 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Installing TextLint on top of PharoKernel

by Pavel Krivanek

Hi, On Sat, Sep 3, 2011 at 9:03 PM, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > Hi Damien > > I wanted to see the call stack with a script testHTTPSocket.st: > > HTTPSocket > Â Â Â Â httpGet: 'http://source.lukas-renggli.ch/petit/?C=M;O=D' > Â Â Â Â args: nil > Â Â Â Â user: '' > Â Â Â Â passwd: '' it works for me on the Gofer image https://ci.lille.inria.fr/pharo/view/Pharo-Kernel/job/Pharo%20Kernel%20Gofe… > without quitting, opened the PharoKernel window (it is minimized in my > WinXP) and in the VM Preferences -> Debug options -> dump call stack > It seems there is a recursive MNU: > > Process > 156305476 Semaphore>critical: > 156305384 BlockClosure>ensure: > 156305000 Semaphore>critical: > 156304908 Mutex>critical: > 156304816 ThreadSafeTranscript>nextPutAll: > 156298960 ThreadSafeTranscript>print: > 156298868 ThreadSafeTranscript>show: > 156127516 DummyUIManager>unhandledErrorDefaultAction: > 156127424 UnhandledError>defaultAction > 156127332 UndefinedObject>handleSignal: > 156127204 Exception>signal > 156127112 >signalForException: > 156127020 Error>defaultAction > 156126928 MessageNotUnderstood>defaultAction > 156126836 UndefinedObject>handleSignal: > 156126700 Exception>signal > 156126608 Object>doesNotUnderstand: uiProcess > 156126492 Message>sentTo: > 156119292 Object>doesNotUnderstand: uiProcess > 156119176 Message>sentTo: > 156116884 Object>doesNotUnderstand: uiProcess > 156116768 Message>sentTo: > .... > > Then I evaluated basicTest.st > > ^3+4. > SmalltalkImage current snapshot: false andQuit: true. you can not use return (^) here. > >>Pharo -headless PharoKernel-Gofer-1.4.image basicTest.st > out.txt > > out.txt is empty and I have a PharoDebug.log > > loadGofer.st > Error: > SyntaxErrorNotification > 85 > 1 [:t1 | > | t2 | > t2 := FileStream forceNewFileNamed: 'PharoDebug.log'. > Â Â Â Â t2 nextPutAll: 'loadGofer.st'; > Â Â Â Â Â Â Â Â cr. > Â Â Â Â t2 nextPutAll: 'Error:'; > Â Â Â Â Â Â Â Â cr. > Â Â Â Â t2 nextPutAll: t1 asString; > Â Â Â Â Â Â Â Â cr. > Â Â Â Â t2 nextPutAll: thisContext stack size asString; > Â Â Â Â Â Â Â Â cr. > Â Â Â Â thisContext stack copy > Â Â Â Â Â Â Â Â withIndexDo: [:t3 :t4 | [t2 nextPutAll: t4 asString; > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â space; > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â nextPutAll: t3 asString; > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â cr] > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â ifError: [:t5 | t2 nextPutAll: t5 asString; > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â cr]]. > Â Â Â Â t2 close. > Â Â Â Â Smalltalk quitPrimitive] in UndefinedObject>>DoIt > 2 BlockClosure>>cull: > .... > > 2011/9/3 Damien Cassou <damien.cassou(a)gmail.com>: -- Pavel >> Hi, >> >> I tried to download PharoKernel and execute the following script but >> nothing happens: >> >> Gofer new >> Â renggli: 'petit'; >> Â package: 'PetitParser'; >> Â load. >> Gofer new >> Â squeaksource: 'textlint'; >> Â package: 'TextLint-Model'; >> Â package: 'TextLint-Console'; >> Â load. >> WorldState addDeferredUIMessage: [ SmalltalkImage current snapshot: >> true andQuit: true ]. >> >> >> I got PharoKernel from >> https://ci.lille.inria.fr/pharo/view/Pharo-Kernel/job/Pharo%20Kernel%20Gofe… >> >> Thank you >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Lambdas are relegated to relative obscurity until Java makes them >> popular by not having them." James Iry >> >> > >

Sept. 3, 2011

Re: [Pharo-project] PetitSmalltalk: now with a self-contained grammar for number literals

by Frank Shearar

On 3 September 2011 19:35, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > 2011/9/3 Frank Shearar <frank.shearar(a)gmail.com>: >> On 3 September 2011 18:50, Lukas Renggli <renggli(a)gmail.com> wrote: >>> I think it is a good idea to have the number parser separate, after >>> all it might also make sense to use it separately. >>> >>> It seems that the new Smalltalk grammar is significantly slower. The >>> benchmark PPSmalltalkClassesTests class>>#benchmark: that uses the >>> source code of the collection hierarchy and does not especially target >>> number literals runs 30% slower. >>> >>> Also I see that "Number readFrom: ..." is still used within the >>> grammar. This seems to be a bit strange, no? >> >> Yes: it's a double-parse, which is a bit lame. First, we parse the >> literal with PPSmalltalkNumberParser, which ensures that the thing >> given to Number class >> #readFrom: is a well-formed token (so, in >> particular, Squeak's Number doesn't get to see anything other than a >> well-formed token). >> >> It sounds like you're happy with the basic concept, so maybe I should >> remove the Number class >> #readFrom: stuff, see if I can't remove the >> performance issues, and resubmit the patch. >> >> frank >> > > Yes, a NumberParser is essentially parsing, and this duplication sounds useless. It's bad for performance but it's definitely not useless: it removes the platform-dependent issues around Number class >> #readFrom:. In Squeak we use the ExtendedNumberParser which will quite happily accept '1.' as a valid number. This way, #readFrom: definitely gets a valid Smalltalk number literal. frank > The main feature of interest in NumberParser that I consider a > requirement and should find its equivalence in a PetitNumberParser is: > - round a decimal representation to nearest Float > It's simple, just convert a Fraction asFloat in a single final step to > avoid cumulating round off errors - see > #makeFloatFromMantissa:exponent:base: > > The second feature of interest in NumberParser is the ability to > parser LargeInteger efficiently by avoiding (10 * largeValue + > digitValue) loops, and replacing them with a log(n) cost. > This would be a simple thing to implement in a functional language. > > Nicolas > >>> Lukas >>> >>> >>> On 3 September 2011 17:18, Frank Shearar <frank.shearar(a)gmail.com> wrote: >>>> On 3 September 2011 15:56, Lukas Renggli <renggli(a)gmail.com> wrote: >>>>> On 3 September 2011 16:51, Frank Shearar <frank.shearar(a)gmail.com> wrote: >>>>>> Hi Lukas, >>>>>> >>>>>> I haven't :) mainly because I'm unsure where to put it - is there >>>>>> perhaps a PP Inbox, or shall I just post the merged version, or what's >>>>>> your preference? (How about an mcd between my merge and PP's head?) >>>>> >>>>> Just put the .mcz at some public URL (dropbox, squeak source, ...) or >>>>> attach it to a mail. >>>> >>>> Ah, great - here it is. You'll see I've written the grammar as a >>>> separate class. That was really more to make what I'd done more >>>> obvious and to minimise the change to PPSmalltalkGrammar, but perhaps >>>> it's not a bad idea anyway: it's easy to see the number literal >>>> subgrammar. >>>> >>>> frank >>>> >>>>> Lukas >>>>> >>>>> -- >>>>> Lukas Renggli >>>>> www.lukas-renggli.ch >>>>> >>>>> >>>> >>> >>> >>> >>> -- >>> Lukas Renggli >>> www.lukas-renggli.ch >>> >>> >> >> > >

Sept. 3, 2011

Re: [Pharo-project] Installing TextLint on top of PharoKernel

by HernÃ¡n Morales Durand

Hi Damien I wanted to see the call stack with a script testHTTPSocket.st: HTTPSocket httpGet: 'http://source.lukas-renggli.ch/petit/?C=M;O=D' args: nil user: '' passwd: '' without quitting, opened the PharoKernel window (it is minimized in my WinXP) and in the VM Preferences -> Debug options -> dump call stack It seems there is a recursive MNU: Process 156305476 Semaphore>critical: 156305384 BlockClosure>ensure: 156305000 Semaphore>critical: 156304908 Mutex>critical: 156304816 ThreadSafeTranscript>nextPutAll: 156298960 ThreadSafeTranscript>print: 156298868 ThreadSafeTranscript>show: 156127516 DummyUIManager>unhandledErrorDefaultAction: 156127424 UnhandledError>defaultAction 156127332 UndefinedObject>handleSignal: 156127204 Exception>signal 156127112 >signalForException: 156127020 Error>defaultAction 156126928 MessageNotUnderstood>defaultAction 156126836 UndefinedObject>handleSignal: 156126700 Exception>signal 156126608 Object>doesNotUnderstand: uiProcess 156126492 Message>sentTo: 156119292 Object>doesNotUnderstand: uiProcess 156119176 Message>sentTo: 156116884 Object>doesNotUnderstand: uiProcess 156116768 Message>sentTo: .... Then I evaluated basicTest.st ^3+4. SmalltalkImage current snapshot: false andQuit: true. >Pharo -headless PharoKernel-Gofer-1.4.image basicTest.st > out.txt out.txt is empty and I have a PharoDebug.log loadGofer.st Error: SyntaxErrorNotification 85 1 [:t1 | | t2 | t2 := FileStream forceNewFileNamed: 'PharoDebug.log'. t2 nextPutAll: 'loadGofer.st'; cr. t2 nextPutAll: 'Error:'; cr. t2 nextPutAll: t1 asString; cr. t2 nextPutAll: thisContext stack size asString; cr. thisContext stack copy withIndexDo: [:t3 :t4 | [t2 nextPutAll: t4 asString; space; nextPutAll: t3 asString; cr] ifError: [:t5 | t2 nextPutAll: t5 asString; cr]]. t2 close. Smalltalk quitPrimitive] in UndefinedObject>>DoIt 2 BlockClosure>>cull: .... 2011/9/3 Damien Cassou <damien.cassou(a)gmail.com>: > Hi, > > I tried to download PharoKernel and execute the following script but > nothing happens: > > Gofer new > Â renggli: 'petit'; > Â package: 'PetitParser'; > Â load. > Gofer new > Â squeaksource: 'textlint'; > Â package: 'TextLint-Model'; > Â package: 'TextLint-Console'; > Â load. > WorldState addDeferredUIMessage: [ SmalltalkImage current snapshot: > true andQuit: true ]. > > > I got PharoKernel from > https://ci.lille.inria.fr/pharo/view/Pharo-Kernel/job/Pharo%20Kernel%20Gofe… > > Thank you > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Lambdas are relegated to relative obscurity until Java makes them > popular by not having them." James Iry > >

Sept. 3, 2011

Re: [Pharo-project] PetitSmalltalk: now with a self-contained grammar for number literals

by Nicolas Cellier

2011/9/3 Frank Shearar <frank.shearar(a)gmail.com>: > On 3 September 2011 18:50, Lukas Renggli <renggli(a)gmail.com> wrote: >> I think it is a good idea to have the number parser separate, after >> all it might also make sense to use it separately. >> >> It seems that the new Smalltalk grammar is significantly slower. The >> benchmark PPSmalltalkClassesTests class>>#benchmark: that uses the >> source code of the collection hierarchy and does not especially target >> number literals runs 30% slower. >> >> Also I see that "Number readFrom: ..." is still used within the >> grammar. This seems to be a bit strange, no? > > Yes: it's a double-parse, which is a bit lame. First, we parse the > literal with PPSmalltalkNumberParser, which ensures that the thing > given to Number class >> #readFrom: is a well-formed token (so, in > particular, Squeak's Number doesn't get to see anything other than a > well-formed token). > > It sounds like you're happy with the basic concept, so maybe I should > remove the Number class >> #readFrom: stuff, see if I can't remove the > performance issues, and resubmit the patch. > > frank > Yes, a NumberParser is essentially parsing, and this duplication sounds useless. The main feature of interest in NumberParser that I consider a requirement and should find its equivalence in a PetitNumberParser is: - round a decimal representation to nearest Float It's simple, just convert a Fraction asFloat in a single final step to avoid cumulating round off errors - see #makeFloatFromMantissa:exponent:base: The second feature of interest in NumberParser is the ability to parser LargeInteger efficiently by avoiding (10 * largeValue + digitValue) loops, and replacing them with a log(n) cost. This would be a simple thing to implement in a functional language. Nicolas >> Lukas >> >> >> On 3 September 2011 17:18, Frank Shearar <frank.shearar(a)gmail.com> wrote: >>> On 3 September 2011 15:56, Lukas Renggli <renggli(a)gmail.com> wrote: >>>> On 3 September 2011 16:51, Frank Shearar <frank.shearar(a)gmail.com> wrote: >>>>> Hi Lukas, >>>>> >>>>> I haven't :) mainly because I'm unsure where to put it - is there >>>>> perhaps a PP Inbox, or shall I just post the merged version, or what's >>>>> your preference? (How about an mcd between my merge and PP's head?) >>>> >>>> Just put the .mcz at some public URL (dropbox, squeak source, ...) or >>>> attach it to a mail. >>> >>> Ah, great - here it is. You'll see I've written the grammar as a >>> separate class. That was really more to make what I'd done more >>> obvious and to minimise the change to PPSmalltalkGrammar, but perhaps >>> it's not a bad idea anyway: it's easy to see the number literal >>> subgrammar. >>> >>> frank >>> >>>> Lukas >>>> >>>> -- >>>> Lukas Renggli >>>> www.lukas-renggli.ch >>>> >>>> >>> >> >> >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> >> > >

Sept. 3, 2011

Re: [Pharo-project] PetitSmalltalk: now with a self-contained grammar for number literals

by Lukas Renggli

That sounds like a good plan. I would expect the PetitParser performance to be slightly slower than the one of the hand-written number parser. However, I would not expect a significant performance difference on normal source code where most tokens are not numbers. Lukas On 3 September 2011 20:07, Frank Shearar <frank.shearar(a)gmail.com> wrote: > On 3 September 2011 18:50, Lukas Renggli <renggli(a)gmail.com> wrote: >> I think it is a good idea to have the number parser separate, after >> all it might also make sense to use it separately. >> >> It seems that the new Smalltalk grammar is significantly slower. The >> benchmark PPSmalltalkClassesTests class>>#benchmark: that uses the >> source code of the collection hierarchy and does not especially target >> number literals runs 30% slower. >> >> Also I see that "Number readFrom: ..." is still used within the >> grammar. This seems to be a bit strange, no? > > Yes: it's a double-parse, which is a bit lame. First, we parse the > literal with PPSmalltalkNumberParser, which ensures that the thing > given to Number class >> #readFrom: is a well-formed token (so, in > particular, Squeak's Number doesn't get to see anything other than a > well-formed token). > > It sounds like you're happy with the basic concept, so maybe I should > remove the Number class >> #readFrom: stuff, see if I can't remove the > performance issues, and resubmit the patch. > > frank > >> Lukas >> >> >> On 3 September 2011 17:18, Frank Shearar <frank.shearar(a)gmail.com> wrote: >>> On 3 September 2011 15:56, Lukas Renggli <renggli(a)gmail.com> wrote: >>>> On 3 September 2011 16:51, Frank Shearar <frank.shearar(a)gmail.com> wrote: >>>>> Hi Lukas, >>>>> >>>>> I haven't :) mainly because I'm unsure where to put it - is there >>>>> perhaps a PP Inbox, or shall I just post the merged version, or what's >>>>> your preference? (How about an mcd between my merge and PP's head?) >>>> >>>> Just put the .mcz at some public URL (dropbox, squeak source, ...) or >>>> attach it to a mail. >>> >>> Ah, great - here it is. You'll see I've written the grammar as a >>> separate class. That was really more to make what I'd done more >>> obvious and to minimise the change to PPSmalltalkGrammar, but perhaps >>> it's not a bad idea anyway: it's easy to see the number literal >>> subgrammar. >>> >>> frank >>> >>>> Lukas >>>> >>>> -- >>>> Lukas Renggli >>>> www.lukas-renggli.ch >>>> >>>> >>> >> >> >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> >> > > -- Lukas Renggli www.lukas-renggli.ch

Sept. 3, 2011

Re: [Pharo-project] PetitSmalltalk: now with a self-contained grammar for number literals

by Frank Shearar

On 3 September 2011 18:50, Lukas Renggli <renggli(a)gmail.com> wrote: > I think it is a good idea to have the number parser separate, after > all it might also make sense to use it separately. > > It seems that the new Smalltalk grammar is significantly slower. The > benchmark PPSmalltalkClassesTests class>>#benchmark: that uses the > source code of the collection hierarchy and does not especially target > number literals runs 30% slower. > > Also I see that "Number readFrom: ..." is still used within the > grammar. This seems to be a bit strange, no? Yes: it's a double-parse, which is a bit lame. First, we parse the literal with PPSmalltalkNumberParser, which ensures that the thing given to Number class >> #readFrom: is a well-formed token (so, in particular, Squeak's Number doesn't get to see anything other than a well-formed token). It sounds like you're happy with the basic concept, so maybe I should remove the Number class >> #readFrom: stuff, see if I can't remove the performance issues, and resubmit the patch. frank > Lukas > > > On 3 September 2011 17:18, Frank Shearar <frank.shearar(a)gmail.com> wrote: >> On 3 September 2011 15:56, Lukas Renggli <renggli(a)gmail.com> wrote: >>> On 3 September 2011 16:51, Frank Shearar <frank.shearar(a)gmail.com> wrote: >>>> Hi Lukas, >>>> >>>> I haven't :) mainly because I'm unsure where to put it - is there >>>> perhaps a PP Inbox, or shall I just post the merged version, or what's >>>> your preference? (How about an mcd between my merge and PP's head?) >>> >>> Just put the .mcz at some public URL (dropbox, squeak source, ...) or >>> attach it to a mail. >> >> Ah, great - here it is. You'll see I've written the grammar as a >> separate class. That was really more to make what I'd done more >> obvious and to minimise the change to PPSmalltalkGrammar, but perhaps >> it's not a bad idea anyway: it's easy to see the number literal >> subgrammar. >> >> frank >> >>> Lukas >>> >>> -- >>> Lukas Renggli >>> www.lukas-renggli.ch >>> >>> >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch > >

Sept. 3, 2011

Re: [Pharo-project] PetitSmalltalk: now with a self-contained grammar for number literals

by Lukas Renggli

I think it is a good idea to have the number parser separate, after all it might also make sense to use it separately. It seems that the new Smalltalk grammar is significantly slower. The benchmark PPSmalltalkClassesTests class>>#benchmark: that uses the source code of the collection hierarchy and does not especially target number literals runs 30% slower. Also I see that "Number readFrom: ..." is still used within the grammar. This seems to be a bit strange, no? Lukas On 3 September 2011 17:18, Frank Shearar <frank.shearar(a)gmail.com> wrote: > On 3 September 2011 15:56, Lukas Renggli <renggli(a)gmail.com> wrote: >> On 3 September 2011 16:51, Frank Shearar <frank.shearar(a)gmail.com> wrote: >>> Hi Lukas, >>> >>> I haven't :) mainly because I'm unsure where to put it - is there >>> perhaps a PP Inbox, or shall I just post the merged version, or what's >>> your preference? (How about an mcd between my merge and PP's head?) >> >> Just put the .mcz at some public URL (dropbox, squeak source, ...) or >> attach it to a mail. > > Ah, great - here it is. You'll see I've written the grammar as a > separate class. That was really more to make what I'd done more > obvious and to minimise the change to PPSmalltalkGrammar, but perhaps > it's not a bad idea anyway: it's easy to see the number literal > subgrammar. > > frank > >> Lukas >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> >> > -- Lukas Renggli www.lukas-renggli.ch

Sept. 3, 2011

Re: [Pharo-project] Testing Pharo OneClick 1.3

by HernÃ¡n Morales Durand

2011/9/2 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > > On Sep 2, 2011, at 7:16 AM, HernÃ¡n Morales Durand wrote: > >> Two more: >> >> ScriptLoader new installingInstaller > > should not work and should not be used. > > Nobody should use ScriptLoader :) > I know :) just pointing a way to reproduce a possible problem with Zinc. > >> MNU possibly related with ZnNetworkingUtils url object. >> >> -Enable underscore assignment (some packages still needs this setting >> for loading) >> -Evaluate: >> >> | source mNode | >> source := 'initialize >> Â Â Â | array start stop | >> Â Â Â array _ Array new: 100. >> Â Â Â start _ 0. >> Â Â Â stop _ 0.'. >> mNode := UndefinedObject evaluatorClass new >> Â Â Â compile: source >> Â Â Â in: UndefinedObject >> Â Â Â classified: nil >> Â Â Â notifying: nil >> Â Â Â ifFail: []. >> SyntaxError open: ( SyntaxError new contents: mNode sourceText ). >> >> Hit right-button in the "UndefinedObject Â <none>" line in the >> SyntaxError windows. >> Select "Browse full" >> MNU >> Anyone could reproduce that one? It happened after evaluating: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfVMMaker'; load. ((Smalltalk at: #ConfigurationOfVMMaker) project version: '1.4') load >> 2011/9/1 Damien Cassou <damien.cassou(a)gmail.com>: >>> http://code.google.com/p/pharo/issues/detail?id=4751 >>> >>> On Thu, Sep 1, 2011 at 6:04 PM, HernÃ¡n Morales Durand >>> <hernan.morales(a)gmail.com> wrote: >>>> Generate #= and #hash >>> >>> >>> >>> -- >>> Damien Cassou >>> http://damiencassou.seasidehosting.st >>> >>> "Lambdas are relegated to relative obscurity until Java makes them >>> popular by not having them." James Iry >>>

Sept. 3, 2011

Re: [Pharo-project] PetitSmalltalk: now with a self-contained grammar for number literals

by Frank Shearar

On 3 September 2011 15:56, Lukas Renggli <renggli(a)gmail.com> wrote: > On 3 September 2011 16:51, Frank Shearar <frank.shearar(a)gmail.com> wrote: >> Hi Lukas, >> >> I haven't :) mainly because I'm unsure where to put it - is there >> perhaps a PP Inbox, or shall I just post the merged version, or what's >> your preference? (How about an mcd between my merge and PP's head?) > > Just put the .mcz at some public URL (dropbox, squeak source, ...) or > attach it to a mail. Ah, great - here it is. You'll see I've written the grammar as a separate class. That was really more to make what I'd done more obvious and to minimise the change to PPSmalltalkGrammar, but perhaps it's not a bad idea anyway: it's easy to see the number literal subgrammar. frank > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch > >

Sept. 3, 2011

Re: [Pharo-project] PetitSmalltalk: now with a self-contained grammar for number literals

by Lukas Renggli

On 3 September 2011 16:51, Frank Shearar <frank.shearar(a)gmail.com> wrote: > Hi Lukas, > > I haven't :) mainly because I'm unsure where to put it - is there > perhaps a PP Inbox, or shall I just post the merged version, or what's > your preference? (How about an mcd between my merge and PP's head?) Just put the .mcz at some public URL (dropbox, squeak source, ...) or attach it to a mail. Lukas -- Lukas Renggli www.lukas-renggli.ch

Sept. 3, 2011