April 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [update 2.0] #20007

by Bernardo Ezequiel Contreras

excuse me, where's the build for pharo 2.0? thanks On Fri, Apr 20, 2012 at 12:20 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > 20007 > ----- > > Issue 5610: layout variable on Behavior > http://code.google.com/p/pharo/issues/detail?id=5610 > > PLEASE NOTE: this update adds a fourth iVar in Behavor. > > -> use a old Squeak VM for loading this update > -> the DNU at the end, just force return self. > > ;-) It's called unstable for a reason! > > Camillo and Marcus > > if someone wonders... we want to slowly iterate to reach something like > the stuff > described here: > http://scg.unibe.ch/archive/papers/Verw11bFlexibleObjectLayouts.pdf > > -- > Marcus Denker -- http://marcusdenker.de > > >

April 20, 2012

[Pharo-project] [update 2.0] #20007

by Marcus Denker

20007 ----- Issue 5610: layout variable on Behavior http://code.google.com/p/pharo/issues/detail?id=5610 PLEASE NOTE: this update adds a fourth iVar in Behavor. -> use a old Squeak VM for loading this update -> the DNU at the end, just force return self. ;-) It's called unstable for a reason! Camillo and Marcus if someone wonders... we want to slowly iterate to reach something like the stuff described here: http://scg.unibe.ch/archive/papers/Verw11bFlexibleObjectLayouts.pdf -- Marcus Denker -- http://marcusdenker.de

April 20, 2012

[Pharo-project] How to disable development tools on Pharo 1.4

by Noury Bouraqadi

Hi, I tried it with WorldSwitch-Preferences from SS3. A minor fix was required to have it run on 1.4 (use rehash instead of rehachWithoutBecome not in the system anymore). Attached the fixed version since I can't write on the repo. I get a "closed" image. I don't know how to test it further. Noury Afin de contribuer au respect de l'environnement, merci de n'imprimer ce courriel qu'en cas de necessite Please consider the environment before you print On 2 fÃ©vr. 2012, at 14:32, Esteban Lorenzano wrote: > Hi Noury, > > I packaged what I have. And even create a settings configuration for it (under "Deployment" category). > Notice that is very hacky and ugly and needs a lot (and I mean A LOT) of polish... but is a start :) > > see WSSettings class>>#setDeployment: for a start. > > <WorldSwitch-Preferences-EstebanLorenzano.2.mcz> > > best, > Esteban > > El 02/02/2012, a las 6:40a.m., Noury Bouraqadi escribiÃ³: > >> Hi Esteban, >> >> On 31 janv. 2012, at 14:23, Esteban Lorenzano wrote: >> >>> Hi, >>> >>> in fact, what Mariano posted is just a part... disable everything is complicated, because code is everywhere... I'm collection all of this changes in a package, to see in advance if it is possible to abstract that. >> >> Thanks Esteban! >> Do you have a version of this package already? >> Otherwise, I'll start packaging what Mariano sent. >> >> >>> Ideally, we should have a preference "Disable Development Mode", or something like that to allow desktop developers to easily switch... >>> >> Yes. We should have a menu for this. It's part of dev tools. >> It's a shame that this critical feature isn't available yet. >> >> Noury >> >>> best, >>> Esteban >>> >>> El 31/01/2012, a las 10:16a.m., Ben Coman escribiÃ³: >>> >>>> Noury Bouraqadi wrote: >>>>> I remember having seen some time in the past a menu that allows to shrink the image and disable the world menu. >>>>> But, I can't retrieve any thing related. I don't care about the menu per se. I'd be happy with a message to send to some object that does the job. >>>>> >>>>> >>>>> Noury >>>>> -- >>>>> http://twitter.com/#!/NouryBouraqadi >>>>> http://www.kroobe.com/profile/noury >>>>> >>>>> >>>> Squeak 3.9 based, but perhaps something useful... >>>> "Prepare For Application Deployment" http://squeak.preeminent.org/tut2007/html/205.html >>>> >>>> >>> >>> >> >> Noury >> -- >> http://twitter.com/#!/NouryBouraqadi >> http://www.kroobe.com/profile/noury >> >> >> Afin de contribuer au respect de l'environnement, >> merci de n'imprimer ce courriel qu'en cas de necessite >> >> Please consider the environment before you print >> >> >> >> > Noury -- http://twitter.com/#!/NouryBouraqadi http://www.kroobe.com/profile/noury

April 20, 2012

Re: [Pharo-project] [NativeBoost] Generic failure errors when using nil for void* and char* arguments

by Jan van de Sandt

Yes, now it works! Thanks Igor. On Fri, Apr 20, 2012 at 4:46 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 20 April 2012 15:59, Jan van de Sandt <jvdsandt(a)gmail.com> wrote: > > Hello, > > > > I use NativeBoost to call some icu4c functions. This works fine most of > the > > time. But now I run into the problem that when I pass nil as the argument > > value for one or more void* / char* parameters I get an error. When I > pass a > > value or an empty ByteArray than it works. > > > > According to the icu4c documentation I should be able to pass NULL as an > > argument value. > > > > What am I missing? > > > > For pointers, there is an options in callouts, #optCoerceNilToNull > which should be set, > then you can invoke the call with nil as argument, which will convert > it to C NULL. > > By default this option is OFF, because extra check means extra cycles. > > You can control a callout options by either per function call (see > NBBasicExamples>>readDoubleFrom:) > or for all methods of your class as a whole, like: > > MyClass class>>ffiCalloutOptions > "by default, return all pointers as an instance of external address > " > ^ #( > + optReturnPtrAsExternalAddress > + optCoerceNilToNull "passing nil as pointer, will convert > it to null(0) " > ) > > > Jan. > > > > -- > Best regards, > Igor Stasenko. > >

April 20, 2012

Re: [Pharo-project] [NativeBoost] Generic failure errors when using nil for void* and char* arguments

by Igor Stasenko

On 20 April 2012 15:59, Jan van de Sandt <jvdsandt(a)gmail.com> wrote: > Hello, > > I use NativeBoost to call some icu4c functions. This works fine most of the > time. But now I run into the problem that when I pass nil as the argument > value for one or more void* / char* parameters I get an error. When I pass a > value or an empty ByteArray than it works. > > According to the icu4c documentation I should be able to pass NULL as an > argument value. > > What am I missing? > For pointers, there is an options in callouts, #optCoerceNilToNull which should be set, then you can invoke the call with nil as argument, which will convert it to C NULL. By default this option is OFF, because extra check means extra cycles. You can control a callout options by either per function call (see NBBasicExamples>>readDoubleFrom:) or for all methods of your class as a whole, like: MyClass class>>ffiCalloutOptions "by default, return all pointers as an instance of external address " ^ #( + optReturnPtrAsExternalAddress + optCoerceNilToNull "passing nil as pointer, will convert it to null(0) " ) > Jan. -- Best regards, Igor Stasenko.

April 20, 2012

Re: [Pharo-project] [update 2.0] #20006

by Guillermo Polito

:D Thanks!! On Fri, Apr 20, 2012 at 4:26 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > 20006 > ----- > > Issue 5615: clean up #contextForLocalVariables > http://code.google.com/p/pharo/issues/detail?id=5615 > > > -- > Marcus Denker -- http://marcusdenker.de > > >

April 20, 2012

[Pharo-project] [update 2.0] #20006

by Marcus Denker

20006 ----- Issue 5615: clean up #contextForLocalVariables http://code.google.com/p/pharo/issues/detail?id=5615 -- Marcus Denker -- http://marcusdenker.de

April 20, 2012

Re: [Pharo-project] Monticello enhancement - Repository browser <changes from last version>

by Damien Cassou

On Fri, Apr 20, 2012 at 3:26 PM, Ben Coman <btc(a)openinworld.com> wrote: > This is an idea for an enhancement to the Monticello Repository browser that > at least myself and perhaps others would find useful - or maybe this is > already exists and I just don't know about it. 1- Select the version you want to study 2- Press the 'History' button 3- Select the version you want to compare to (the second in the list in your scenario) 4- Right click and select 'View changes' Is it what you want? -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

April 20, 2012

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

by Frank Shearar

On 20 April 2012 03:51, Levente Uzonyi <leves(a)elte.hu> wrote: > On Thu, 19 Apr 2012, Frank Shearar wrote: > >> I found a serious bug in parsing numbers with negative exponents. It >> was completey broken, in fact, parsing 1e-1 as 10, not 1 / 10. Anyway. >> This version fixes that, and adds a bunch of tests demonstrating that >> number parsing will return rationals if it can. >> >> It's significantly slower than Squeak's SqNumberParser: >> >> Time millisecondsToRun: [100000 timesRepeat: [SqNumberParser parse: >> '1234567890']] => 466 >> >> Time millisecondsToRun: [100000 timesRepeat: [PPSmalltalkNumberParser >> parse: '1234567890']] => 32082 >> >> I've attached a MessageTally spying on the latter: I've not much skill >> in reading these, but nothing leaps out at me as being obviously >> awful. > > > Didn't check the code, just the tally, and I think that > PPSmalltalkNumberParser(PPSmalltalkNumberGrammar)>>digitsBase: is begging > for optimization. It's probably also the cause of the high amount of garbage > which causes significant amount of time spent with garbage collection. > It's also interesting is that the finalization process does so much work, > there may be something wrong with your image. Thanks for taking a look, Levente. I'd expect digitsBase: to dominate the running costs, given that we're parsing numbers. I do make a large number of throwaway "immutable" values with a Builder-like pattern... in PPSmalltalkNumberParser >> #makeNumberFrom:base:. That, I would imagine, could explain the garbage? If I may, what do you look for when reading the MessageTally? How do you tell, for instance, that there's excessive garbage production? That the incremental GCs take 7ms? (I'm reading Andreas' comments on http://wiki.squeak.org/squeak/4210 again.) frank > Levente > > >> >> frank >> >> On 14 September 2011 20:26, Frank Shearar <frank.shearar(a)gmail.com> wrote: >>> >>> 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. >>>> 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. >>> >>> >>> Hopefully this won't offend your sensibilities too much :). It does, >>> in fact, use 10* loops - I wrote an experimental "front half * rear >>> half" recursion, which was slower in my benchmarks. >>> >>> This version has the grammar and parser doing no string->number >>> conversion at all. PPSmalltalkNumberMaker supplies a number of utility >>> methods designed to stop one from making malformed numbers. It also >>> supplies a builder interface that the parser uses to construct >>> numbers. >>> >>> frank >>> >>>> 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 >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >> >

April 20, 2012

Re: [Pharo-project] 1.4, seaside, comet, how to get it working

by Sven Van Caekenberghe

On 20 Apr 2012, at 15:29, Igor Stasenko wrote: > On 20 April 2012 13:46, Sven Van Caekenberghe <sven(a)beta9.be> wrote: >> JB, >> >> On 19 Apr 2012, at 19:19, jb wrote: >> >>> i just downloaded 1.4, installed seaside using the configuration browser and everything went great. >>> >>> i added a Zinc server adapator in the Seaside control panel and its all working fine. >>> >>> but then i went to set up the comet/streaming server and im kind of stumped. there is only one kind of Zinc server adapter and when i try to use it for the comet examples they all complain about needing a server that supports streaming. >>> >>> what do i need to do to get a streaming server for the comet applications? >>> >>> thanks in advance! >>> >>> jb >> >> As author of Zinc I would like to help you, but I don't know what functionality is expected from a server that 'supports streaming'. If you or someone else could refer me to code and/or documentation that describes what should be there, maybe I can try to help you. >> > > If you remember we discussed that before. Mainly it is about getting > a stream for contents from HTTP response. > i.e. something like: > > 'http://x.y.z' asUrl getContents > where you get all contents at once, versus > > 'http://x.y.z' asUrl getContentStream > where you get only a stream and can read incrementally from it. I don't really remember ;-) But I think I more or less begin to understand: some Seaside (client) code wants to access the underlying socket stream to the client ? For reading and/or for writing ? Inside or outside an existing request/response ? Inside or outside the dynamic context of the request handling ? In any case, this seems dangerous. Can I read something about the intended use of this somewhere ? Example usage code ? >> Sven >> >> >> -- >> Sven Van Caekenberghe >> http://stfx.eu >> Smalltalk is the Red Pill >> >> >> >> >> > > > > -- > Best regards, > Igor Stasenko. >

April 20, 2012