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

[Pharo-project] :)

by StÃ©phane Ducasse

roel wuyts sent me that nice snippet :) | wishStream adjectives | wishStream := WriteStream with: 'For 2011 I wish you '. adjectives := { 'fun' . 'exotic' . 'brilliant' . 'extraordinary' }. { 'research' . 'students' . 'artefacts' . 'conferences'} do: [:e | wishStream nextPutAll: adjectives atRandom; space; nextPutAll: e] separatedBy: [wishStream nextPutAll: ', ']. wishStream nextPutAll: ' and of course good health!'. ^wishStream contents

Jan. 1, 2011

Re: [Pharo-project] new Cog VMs

by Eliot Miranda

Hi All, there are new versions of both the SimpleStackBasedCogit and the StackToRegisterMappingCogit Cog VMs in VM.r2337/<http://www.mirandabanda.org/files/Cog/VM/VM.r2337/> & VM.r2338/ <http://www.mirandabanda.org/files/Cog/VM/VM.r2338/> respectively. These contain fixes for another bad pc mapping bug that could cause hard crashes when jitting on a backward branch in a looping interpreted method. If you're trying to reproduce Cog crashes please upgrade to one of tthese two VMs. TIA and happy new 2011, P.S. according to an FBF RT @dpp RT @giuliodeluise 2011 is a prime number & the sum of 11 consecutive prime numbers: 2011=157+163+167+173+179+181+191+193+197+199+211 Eliot On Thu, Dec 30, 2010 at 6:02 PM, Eliot Miranda <eliot.miranda(a)gmail.com>wrote: > Hi All, > > I've released a new version of Cog that has a substantially improved > code generator along the lines of Peter Deutsch's HPS (VisualWorks) and > various of Ian Piumarta's VMs. These all use a simple tecnique to identify > constant references in bytecode and to support a register-based calling > convention. While this does produce faster code it tends to accelerate > low-level code much more than high-level code as you can see by the > following benchmarks: > > SimpleStackBasedCogit: [1 to: 100000000 do: [:i|]] timeToRun 691 > StackToRegisterMappingCogit: [1 to: 100000000 do: [:i|]] timeToRun 192 > 192 - 691 / 6.91 -72% > > SimpleStackBasedCogit: 0 tinyBenchmarks '753495217 bytecodes/sec; 64769127 > sends/sec' > StackToRegisterMappingCogit: 0 tinyBenchmarks '931756141 bytecodes/sec; > 128157989 sends/sec' > 931756141 - 753495217 / 7534952.17 -24% > 128157989 - 64769127 / 647691.27 -98% > > SimpleStackBasedCogit: [Compiler recompileAll] timeToRun 47013 (no > transcript > StackToRegisterMappingCogit: [Compiler recompileAll] timeToRun 43406 (no > transcript) > 43406 - 47013 / 470.13 -7.67234594686576 > > The status of this code is essentially beta. The test suite runs the same > on the new code generator as on the old, but I think there are still bugs > because I get the occasional transient error. I am therefore very > interested in any reproducible errors you can find. > > The VMs (http://www.mirandabanda.org/files/Cog/VM/VM.r2334/) contain a few > other important changes: > > - a bug fix to bytecode<->native pc mappng that produced incorrect results > for methods containing blocks with ^-returns in them. One symptom is > incorrect highlighting of the pc in the debugger, althoguh symptoms could be > much serious. > > - jitting interpreted methods on backward branches. Currently any > interpreted method that performs more than 20 backward branches will be > considered for JIT compilation and if it is suitable (default, <= 60 > literals) will be compiled to native code. > > - new callback support. I need to commit some changes to the Alien package > to provide access to this but essentially the VM's callback support is now > able to be ported to architectures with register-based calling conventions > (ARM, PowerPC, SPARC etc). I'll try and get the Alien code released soon, > and to back-port the changes to the standard VM before the end of the > holiday. > > One thing that is still /not/ fixed is the lack of a SoundPlugin on win32. > Apologies. I'll try and get a fix for this before the end of the holidays > too, but time might be too tight. There are other priorities such as > harmonising the standard and Cog VMs for the 4.2 release. > > best > Eliot > >

Jan. 1, 2011

Re: [Pharo-project] An intuitive (or screwed) #copyFrom:

by Schwab,Wilhelm K

+1 ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] Sent: Saturday, January 01, 2011 2:59 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] An intuitive (or screwed) #copyFrom: I like copyStateFrom: as a name lukas there is copyFrom:to: and copyFrom: make a lot of sense as copyFrom: index until the end. Stef

Jan. 1, 2011

Re: [Pharo-project] Issue 3436 in pharo: #copyFrom: is broken

by pharo＠googlecode.com

Updates: Status: Accepted Labels: Milestone-1.3 Comment #4 on issue 3436 by stephane.ducasse: #copyFrom: is broken http://code.google.com/p/pharo/issues/detail?id=3436 I suggest to use copyStateFrom: and add copyFrom: in String.

Jan. 1, 2011

Re: [Pharo-project] An intuitive (or screwed) #copyFrom:

by Igor Stasenko

On 1 January 2011 20:59, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > I like copyStateFrom: as a name > > lukas > Â Â Â Â there is copyFrom:to: > Â Â Â Â and copyFrom: make a lot of sense as copyFrom: index until the end. > +1 in the presence of #copyFrom:to: the current implementation of #copyFrom: is misleading. We should pick another name to reflect a completely different behavior. > Stef > > -- Best regards, Igor Stasenko AKA sig.

Jan. 1, 2011

[Pharo-project] Xtreams updates: positioning, slicing and stitching

by mkobetic＠gmail.com

I updated the Xtreams port (http://www.squeaksource.com/Xtreams) over the holidays to catch up with the state on VW side. The primary changes are updates/fixes of the positioning API and a cleanup/extension of the slicing API. The slicers are replaced by much simpler #slicing setup and the inverse, #stitching, was added (the updated documentation can be found in the usual place: http://code.google.com/p/xtreams/wiki/Substreams) More details on the changes below. Enjoy, Martin Positioning updates: * ++/--/+=/-=/position: now return the argument instead of self * they all also skip as far as they can raising Incomplete with the count of the actual amount skipped * this means that the positioning wrapper will advance as far forward as it needs to satisfy the request, in case of -= it means it will advance all the way to the end of the underlying stream. * similarly asking a positioning wrapper for length or available will make it advance to the end * in the other direction, positioning wrapper can't skip past the beginning of its buffer, so if the buffer window moves forward, so does the absolute position; position 0 is always the beginning of the buffer, whereever it is at any given moment * also extended ++ and -- to call the other if the argument is negative (it helps with implementation of the others) All read/write/positioning calls except put:/get/read: now consistently return element counts so that one can use a computation as an argument and then obtain the actual number in response. This simplifies common patterns like: actual := [ stream ++ (x max: y) ] on: Incomplete do: [ :ex | ex count ]. instead of: actual := x max: y. [ stream ++ actual ] on: Incomplete do: [ :ex | actual := ex count ]. Slicing/Stitching updates: Replacing all the -er: slicer creation methods with the new #slicing and adding complementary #stitching. * #slicing is sent to a substream "prototype" and clones it when next slice is needed, e.g. (stream limiting: 3) slicing * #stitching is sent to a read stream of streams and makes it look like one continuous stream [ stream limiting: stream get ] reading stitching * stitching replaces the experimental proto and concatentation streams * ReadStream>>, is now implemented with stitching too

Jan. 1, 2011

Re: [Pharo-project] An intuitive (or screwed) #copyFrom:

by StÃ©phane Ducasse

I like copyStateFrom: as a name lukas there is copyFrom:to: and copyFrom: make a lot of sense as copyFrom: index until the end. Stef

Jan. 1, 2011

Re: [Pharo-project] An intuitive (or screwed) #copyFrom:

by StÃ©phane Ducasse

right please open a bug entry and provide cs :) Stef > Yes, this method name is unfortunate... > > I think we should just rename the method and tag copyFrom: as deprecated. And some versions later we'll implement copyFrom: as we think is appropriate. > > Cheers, > Adrian > > BTW Sebastian, I think your energy would be better invested into producing a changeset and challenging the "invalid"-tag of Henrik in a rational way than to writing a "are you stupid?"-mail.

Jan. 1, 2011

Re: [Pharo-project] An intuitive (or screwed) #copyFrom:

by Schwab,Wilhelm K

Lukas, I must respectfully disagree: it is also quite similar to #copyFrom:to:, and behaves *completely* differently from same. #copyFrom: really should have a more intention-revealing name. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Lukas Renggli [renggli(a)gmail.com] Sent: Saturday, January 01, 2011 2:06 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] An intuitive (or screwed) #copyFrom: Quite some software (Seaside, Mondrian, Magritte, Pier, ...) depends on the current implementation of #copyFrom:, as it is an extremely efficient way to remember and restore the state of an object: rememberReceiverDuring: aBlock previous := self shallowCopy. ^ aBlock ensure: [ self copyFrom: previous ] I don't think that the name of #copyFrom: is misleading (it derives from #copy). What you are looking for is #allButFirst: that goes along with #allButFirst, #allButLast:, allButLast, #first:, and #last:. Cheers, Lukas On 1 January 2011 19:39, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > Wow. In fairness, Dolphin has one or two such oddities. IIRC, the confusion there is that external arrays (DOUBLE, DWORD, etc.) respond to #copyFrom:to: in terms of bytes, not elements. > > The problem in this case appears to be that > > 'a string with some stuff in it' copyFrom:5 > > should blow up because 5 is not a suitable source (a string of some type) from which to copy a string's state. Once it properly reports abuse, we can then move on to asking whether we want a copying selector that can be so easily confused with copying from an index. It might be better named #copyStateFrom:?? > > Sorry to beat the usual drum, but it fits: silent failures need to be hunted down and killed. > > Bill > > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] > Sent: Saturday, January 01, 2011 1:29 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] An intuitive (or screwed) #copyFrom: > > HI sebastian > > If I remember correctly you are not the only one bitten by it :) so we should do something > > Object>>copyFrom: anotherObject > "Copy to myself all instance variables I have in common with anotherObject. This is dangerous because it ignores an object's control over its own inst vars. " > > Now you enumeration is too complex for me :) > >> I ask because, if so, situation goes like this: >> >> A. we think again and decide to do the right thing or we go with the alternative which is >> B. we leave it as invalid, as it is right now, and >> 1. we mislead even to smalltalkers not familiarized to squeak/pharo >> 2. we rationalize some clever way to see it as a feature even if it will mislead everybody (even ourselves in a hurry) >> 3. we lay a foundation to lightly use protocol that is typically used in collections (to do dangerous things like instVar manipulation) >> 4. we break encapsulation and manipulate extremely primitive things in a common sounding selector. >> 5. we work harder on trying to give the impression that we're leaving it like that because we're smarter than the confused people that tried to use it (proving to them that we're dumb) >> 6. we get involved in an unnecessarily complicated way of thinking that will complicate unnecessarily our future (guaranteed) >> 7. we learn how to maintain a screwed attitude in front of people trying to use intuition when using pharo >> 8. we stay comfortable (on the wrong foundation and for the wrong reasons) >> >> That would leave us with this question in the table: >> >> what is compatible with the Pharo's mission? is it A or B? > > My state of mind is always to make the world better :) > > Now > - did you check the senders to copyFrom:? > sounds ok not so many so we could deprecated it easily > > - did you check in other Smalltalk if this method is used or not? > VW not in Object but in probe something > > - did you check the ansi standard? > I guess that this is not there. > > The finder says: > 'if this isn''t broken' . 15 . 'broken' > > no single method, strange.... but indeed > 'if this isn''t broken' . 15 . 20 . 'broken' find copyFrom:to: > > Now what would be a better name > > copyFromObject: > > then > > on String>>copyFrom: ? > > Even if I would prefer (but it sucks) String>>copyFromIndex: but this is more coherent with copyFrom: index to: another > > > Stef > > > > -- Lukas Renggli www.lukas-renggli.ch

Jan. 1, 2011

Re: [Pharo-project] An intuitive (or screwed) #copyFrom:

by Schwab,Wilhelm K

Peter, Feel free to beat me to pointing out silent failures; I'm glad I'm not alone in seeing them as something to be found and eliminated, and it never hurts for the truth to be heard from multiple directions. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Peter Hugosson-Miller [oldmanlink(a)gmail.com] Sent: Saturday, January 01, 2011 2:30 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] An intuitive (or screwed) #copyFrom: Hehehe. While I was considering whether or not to chip in on this thread, two thoughts passed through my mind. The first was that this is one of those annoying silent failures that Wilhelm would surely pick up on (so I didn't need to bring it up). The second was that #copyFrom: really should be called #copyStateFrom: to more accurately reflect what it does, and should be used for. So now this reply is completely redundant, since Wilhelm also suggested the same thing, or maybe I should just stop here and write "+1" instead :-p -- Cheers, Peter On Sat, Jan 1, 2011 at 7:39 PM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu<mailto:bschwab@anest.ufl.edu>> wrote: Wow. In fairness, Dolphin has one or two such oddities. IIRC, the confusion there is that external arrays (DOUBLE, DWORD, etc.) respond to #copyFrom:to: in terms of bytes, not elements. The problem in this case appears to be that 'a string with some stuff in it' copyFrom:5 should blow up because 5 is not a suitable source (a string of some type) from which to copy a string's state. Once it properly reports abuse, we can then move on to asking whether we want a copying selector that can be so easily confused with copying from an index. It might be better named #copyStateFrom:?? Sorry to beat the usual drum, but it fits: silent failures need to be hunted down and killed. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr<mailto:pharo-project-bounces@lists.gforge.inria.fr> [pharo-project-bounces(a)lists.gforge.inria.fr<mailto:pharo-project-bounces@lists.gforge.inria.fr>] On Behalf Of StÃ©phane Ducasse [stephane.ducasse(a)inria.fr<mailto:stephane.ducasse@inria.fr>] Sent: Saturday, January 01, 2011 1:29 PM To: Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> Subject: Re: [Pharo-project] An intuitive (or screwed) #copyFrom: HI sebastian If I remember correctly you are not the only one bitten by it :) so we should do something Object>>copyFrom: anotherObject "Copy to myself all instance variables I have in common with anotherObject. This is dangerous because it ignores an object's control over its own inst vars. " Now you enumeration is too complex for me :) > I ask because, if so, situation goes like this: > > A. we think again and decide to do the right thing or we go with the alternative which is > B. we leave it as invalid, as it is right now, and > 1. we mislead even to smalltalkers not familiarized to squeak/pharo > 2. we rationalize some clever way to see it as a feature even if it will mislead everybody (even ourselves in a hurry) > 3. we lay a foundation to lightly use protocol that is typically used in collections (to do dangerous things like instVar manipulation) > 4. we break encapsulation and manipulate extremely primitive things in a common sounding selector. > 5. we work harder on trying to give the impression that we're leaving it like that because we're smarter than the confused people that tried to use it (proving to them that we're dumb) > 6. we get involved in an unnecessarily complicated way of thinking that will complicate unnecessarily our future (guaranteed) > 7. we learn how to maintain a screwed attitude in front of people trying to use intuition when using pharo > 8. we stay comfortable (on the wrong foundation and for the wrong reasons) > > That would leave us with this question in the table: > > what is compatible with the Pharo's mission? is it A or B? My state of mind is always to make the world better :) Now - did you check the senders to copyFrom:? sounds ok not so many so we could deprecated it easily - did you check in other Smalltalk if this method is used or not? VW not in Object but in probe something - did you check the ansi standard? I guess that this is not there. The finder says: 'if this isn''t broken' . 15 . 'broken' no single method, strange.... but indeed 'if this isn''t broken' . 15 . 20 . 'broken' find copyFrom:to: Now what would be a better name copyFromObject: then on String>>copyFrom: ? Even if I would prefer (but it sucks) String>>copyFromIndex: but this is more coherent with copyFrom: index to: another Stef

Jan. 1, 2011