November 2013 - Pharo-dev - lists.pharo.org

[OT] World Hello Day - November 21, 2013

by Torsten Bergmann

see: http://en.wikipedia.org/wiki/World_Hello_Day so: Transcript show: 'HelloWorld'

Nov. 21, 2013

Re: [Pharo-dev] Fwd: Your request to join pharo-contribution has been accepted

by Sven Van Caekenberghe

On 21 Nov 2013, at 02:18, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > Sven Van Caekenberghe-2 wrote >> I guess this is not yet enough to be able to create a new CI job ? >> Do I still have to wait for a manual approval ? > > > When I was initially added via that process I was not added with either > 'Admin' or 'Project Admin' status. Once Camillo made me an 'admin' I could > create projects. I just made you an 'admin'. If that doesn't stick maybe > one of the others can make it work. Thanks, Paul, I am up and running with my first official CI job: https://ci.inria.fr/pharo-contribution/job/ZTimestamp/ Thanks again, this is an amazing community. Sven

Nov. 21, 2013

SimplePersistence ...

by Torsten Bergmann

... moved to STHub http://smalltalkhub.com/#!/~TorstenBergmann/SimplePersistence with page providing some initial docu and links ... is now on CI https://ci.inria.fr/pharo-contribution/job/SimplePersistence/ ... is GREEN for Pharo20, Pharo30 with stable (3.0) and development (3.0.1) since a few minutes ... is loadable from Config browser in Pharo20 and Pharo3.0 Have fun Torsten and Sean

Nov. 21, 2013

Re: [Pharo-dev] NativeBoost: Documentation Suggestion and Question

by StÃ©phane Ducasse

sean could you propose something for it: adding a class ReadMe? DocuMe? Adding it to the help? Stef On Nov 9, 2013, at 8:21 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > The ESUG presentation this year was very comprehensive. I suggest making the > slides and sample code more prominent/easily accessible from the code. > > Using the presentation, I tried to communicate with the portaudio lib (OSX > 10.8.5, lib installed with brew). > > I did: > PaInitialize > <primitive: #primitiveNativeCall module: #NativeBoostPlugin> > ^ self > nbCall: #(int _Pa_Initialize()) > module: 'libportaudio.dylib' > > The docs list the function name without the underscore, but nm revealed it > with a leading underscore. > > For the module, I tried: > - full path to dylib link above > - fill path to actual versioned dylib file i.e. ...2.dylib > - symlinking both into the VM Plugins folder > > I was thinking maybe this was the indirect function thing like chipmunk, but > even "self nbGetExtenalAddress: 'Pa_Initialize' module: 'libportaudio.dylib' > returned nil. I tried with and without the underscore, with the module > specified all four ways. > > Thanks in advance for any guidance... > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/NativeBoost-Documentation-Suggestion-and-Question-tp4… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Nov. 21, 2013

Re: [Pharo-dev] Is Coral still alive?

by StÃ©phane Ducasse

>> No as far as I know. >> We are thinking to something else - I should discuss with Guillermo. >> the first step for me would be to have a cool OSProcess rewritten with NB. > > which already exists and it's named LIMBO :) Cool. What is its status? > https://github.com/theseion/liblimbo > http://ss3.gemstone.com/ss/Limbo/ We should have a CI :) and move it to SmalltalkHub. Stef

Nov. 21, 2013

Re: [Pharo-dev] Loading Xtreams in Pharo

by StÃ©phane Ducasse

On Nov 20, 2013, at 5:17 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi, > > If anyone else is interested, you can load Xtreams using this expression: > > Gofer new > squeaksource: 'Xtreams'; > configuration; > loadVersion: #bleedingEdge. > > I tested this only in Pharo 3.0, but it should work in 2.0 as well. cool! > > Since all tests are green, it might be a good idea to set up a CI job. > > We could make a new stable config to put in the Configuration Browser repos. +1 Now what I really wonder is - what is the smallest core of Xtreams that we need to load code - could we have it a candleLight > > Sven > >

Nov. 21, 2013

Re: [Pharo-dev] MetaRepoForPharo30 write permissions

by StÃ©phane Ducasse

I thought you were. Strange Stef On Nov 20, 2013, at 9:00 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Hi Torsten, > > thank you very much. Of course I tried it before. I'm not a member of the Smalltalkhub Pharo team so this is the reason why I have to act as explicit contributor. > > Cheers > -- Pavel > > > 2013/11/20 Torsten Bergmann <astares(a)gmx.de> > Done, but I think it should have worked even > without adding you as a contributor. > > > Gesendet: Dienstag, 19. November 2013 um 21:48 Uhr > Von: "Pavel Krivanek" <pavel.krivanek(a)gmail.com> > An: "Discusses Development of Pharo" <pharo-dev(a)lists.pharo.org> > Betreff: [Pharo-dev] MetaRepoForPharo30 write permissions > > Hi, > > can someone add me to the MetaRepoForPharo30 repository? My username is PavelKrivanek. > > Cheers, > -- Pavel > >

Nov. 21, 2013

Re: [Pharo-dev] Fwd: Your request to join pharo-contribution has been accepted

by Paul DeBruicker

err. 'Slave Admin' not 'Project Admin' -- View this message in context: http://forum.world.st/Fwd-Your-request-to-join-pharo-contribution-has-been-… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Nov. 21, 2013

Re: [Pharo-dev] Fwd: Your request to join pharo-contribution has been accepted

by Paul DeBruicker

Sven Van Caekenberghe-2 wrote > I guess this is not yet enough to be able to create a new CI job ? > Do I still have to wait for a manual approval ? When I was initially added via that process I was not added with either 'Admin' or 'Project Admin' status. Once Camillo made me an 'admin' I could create projects. I just made you an 'admin'. If that doesn't stick maybe one of the others can make it work. -- View this message in context: http://forum.world.st/Fwd-Your-request-to-join-pharo-contribution-has-been-… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Nov. 21, 2013

Re: [Pharo-dev] petit parser longest match

by Norbert Hartl

I'm not sure what you are trying to improve. It works quite well :) Norbert > Am 20.11.2013 um 22:59 schrieb Chris Cunningham <cunningham.cb(a)gmail.com>: > > ehh, ignore this for now. Neither is working well enough. If I get something working well, I'll post back. > > >> On Wed, Nov 20, 2013 at 1:45 PM, Chris Cunningham <cunningham.cb(a)gmail.com> wrote: >> Actually, do this [the #( 0 nil ) meant it was shared with ALL choice parsers forever - not a good choice]. >> >> parseOn: aStream >> "This is optimized code that avoids unnecessary block activations, do not change. When all choices fail, the last failure is answered." >> >> | element longest | >> longest := Array with: 0 with: nil. >> 1 to: parsers size do: [ :index | >> element := (parsers at: index) >> parseOn: aStream. >> element isPetitFailure >> ifTrue: [ aStream position > longest first ifTrue: [ longest at: 1 put: aStream position; at: 2 put: element ] ] >> ifFalse: [ ^ element ] ]. >> aStream position: longest first. >> ^ element >> >> >>> On Wed, Nov 20, 2013 at 1:35 PM, Chris Cunningham <cunningham.cb(a)gmail.com> wrote: >>> Ho about this (replacement for yours, or just replace in PPChoiceParser - but it will result in different behavior for that method outside of your particular parser, so beware): >>> >>> parseOn: aStream >>> "This is optimized code that avoids unnecessary block activations, do not change. When all choices fail, the last failure is answered." >>> >>> | element longest | >>> longest := #( 0 nil ). >>> 1 to: parsers size do: [ :index | >>> element := (parsers at: index) >>> parseOn: aStream. >>> element isPetitFailure >>> ifTrue: [ aStream position > longest first ifTrue: [ longest at: 1 put: aStream position; at: 2 put: element ] ] >>> ifFalse: [ ^ element ] ]. >>> aStream position: longest first. >>> ^ element >>> >>> I had a need for it in the past (and, just now, in fact - so minimally tested just now). >>> >>> -cbc >>> >>> >>>> On Wed, Nov 20, 2013 at 2:15 AM, Norbert Hartl <norbert(a)hartl.name> wrote: >>>> I talked to Lukas two years ago about parsing the longest match [1]. He committed it to PetitBeta back then. Now I need it and I had a look at the current parsers but didnât find one that can do the same. Is there a parser that can do longest match? >>>> >>>> If not I would propose adding that to the default petit parser package. Lukasâ proposal back then was >>>> >>>> LongestChoiceParser>>parseOn: aStream >>>> | start element longestEnd longestElement | >>>> start := aStream position. >>>> 1 to: parsers size do: [ :index | >>>> element := (parsers at: index) >>>> parseOn: aStream. >>>> (longestEnd isNil or: [ longestEnd < aStream position ]) ifTrue: [ >>>> longestEnd := aStream position. >>>> longestElement := element ]. >>>> aStream position: start ]. >>>> aStream position: longestEnd. >>>> ^ longestElement >>>> >>>> Norbert >>>> >>>> [1] http://www.iam.unibe.ch/pipermail/moose-dev/2011-July/009365.html >

Nov. 21, 2013