February 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] hashMultiply

by Andres Valloud

Hello... On 2/25/14 18:32 , Martin McClure wrote: > Andres and I have an ongoing discussion on this topic. :-) :)... > And #bitShift *should* be faster. Ok, but how much faster? 64x64 bit multiplication on modern x86 is just 8 cycles (!), and there will likely be parallelism done by the CPU anyway... > But test this. In VW, multiplication > is quite a lot faster than bitShift: for some reason. Unless Andres has > fixed this recently. :-) I haven't measured to see what's going on. In general terms though, unlike with multiplication, on top of the overflow check you also have the argument overflow check because on x86 shl eax, 65 is the same as shl eax, 1 which is obviously not the behavior you want. So that means extra cmp, extra jmp, and you also have to deal with positive / negative arguments to select shl or shr/sar so more cmp and jmp, etc... Note though that IIRC the manual says that for SSE registers, doing something like shl xmm0, 129 is the same as xor xmm0, xmm0 (assembler for the sake of illustratio only) which is nice because then you can combine the overflow check with the argument overflow check. The whole SSE thing though is much, much more than just bitShift. Andres.

Feb. 27, 2014

Fwd: [squeak-dev] Fwd: Floats problem with SIXX between Pharo and GemStone

by Nicolas Cellier

---------- Forwarded message ---------- From: Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> Date: 2014-02-27 0:15 GMT+01:00 Subject: Re: [squeak-dev] Fwd: [Pharo-dev] Floats problem with SIXX between Pharo and GemStone To: The general-purpose Squeak developers list < squeak-dev(a)lists.squeakfoundation.org> 2014-02-26 23:38 GMT+01:00 Tobias Pape <Das.Linux(a)gmx.de>: Can we get this into trunk please? > Ie, > > SqNumberPasrser>>exponentLetters > "current comment" > ^'edqEDQ' > > > Best > -Tobias > > You mean modifying Smalltalk syntax? That's a possible option, and it would work in Pharo too. Note that 1.0E2 was previously interpreted as send #E2 to 1.0, so it might change... ...not much thing : the problem is highly hypothetical, we don't use a leading uppercase letter in selectors usually, and we also put a space before a unary or keyword message - one rare exception I encountered was Complex "constants" like 1+2i ... Begin forwarded message: > > *From: *Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> > *Subject: **Re: [Pharo-dev] Floats problem with SIXX between Pharo and > GemStone* > *Date: *26. Februar 2014 23:14:10 MEZ > *To: *Pharo Development List <pharo-dev(a)lists.pharo.org> > *Reply-To: *Pharo Development List <pharo-dev(a)lists.pharo.org> > > > > > 2014-02-26 23:08 GMT+01:00 Nicolas Cellier < > nicolas.cellier.aka.nice(a)gmail.com>: > >> That's exactly for this kind of reasons that I developped an >> ExtendedNumberParser connected to Number class>>readFrom:, to allow a >> variety of formats used in the rest of the world. >> >> It would have been easy to allow upper letter exponents in this parser, >> but the class was considered superfluous and removed from Pharo 3.0... >> >> super easy is just redefine: > > ExtendedNumberParser>>exponentLetters > ^'edqEDQ' > > and then Float readFrom: '1.0000000000000000E-02' works as expected, that > is in Squeak at least... > > > > > > >

Feb. 26, 2014

Re: [Pharo-dev] iPad version does not work ?[SEC=UNCLASSIFIED]

by Stephen Taylor

On Wed, 2014-02-26 at 08:28 +0100, phil(a)highoctane.be wrote: > You can make it work following the procedure: > http://www.youtube.com/watch?v=7MNsUiCc5FQ&list=UUul18dYQnhOVMfYFg6YSK4A Excellent - I'll watch. > Phil Steve

Feb. 26, 2014

Pharo 3.0 on Mac OS X 10.9

by Sven Van Caekenberghe

Pharo 3.0 on Mac OS X 10.9 The out of the box experience. Installing and running Pharo 3.0 on a blank Mac OS X 10.9 account in 40 seconds. https://www.youtube.com/watch?v=xxljgugI4c4 With 3 extra minutes to demo some networking and image manipulation interactions. Sven -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

Feb. 26, 2014

Re: [Pharo-dev] [Glass] Floats problem with SIXX between Pharo and GemStone

by Martin McClure

On 02/26/2014 01:38 PM, Mariano Martinez Peck wrote: > > So, of course " Float readFrom: '1.0000000000000000E-02' " -> 1.0 This is because Pharo only accepts lower-case letters for exponent ($e $d $q). So if you replace E with e Pharo will parse it as you wish. -Martin

Feb. 26, 2014

Re: [Pharo-dev] Floats problem with SIXX between Pharo and GemStone

by Nicolas Cellier

2014-02-26 23:08 GMT+01:00 Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com>: > That's exactly for this kind of reasons that I developped an > ExtendedNumberParser connected to Number class>>readFrom:, to allow a > variety of formats used in the rest of the world. > > It would have been easy to allow upper letter exponents in this parser, > but the class was considered superfluous and removed from Pharo 3.0... > > super easy is just redefine: ExtendedNumberParser>>exponentLetters ^'edqEDQ' and then Float readFrom: '1.0000000000000000E-02' works as expected, that is in Squeak at least... > 2014-02-26 22:38 GMT+01:00 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > Hi guys, >> >> When I export SmallDoubles with SIXX in GemStone it generates something >> like this: >> >> <sixx.object sixx.id="15" sixx.name="close" sixx.type="SmallDouble" >> >1.0000000000000000E-02</sixx.object> >> >> This is because "0.01 asString" -> '1.0000000000000000E-02' >> >> Then I want to load this in Pharo. So first problem is that of course >> SmallDouble doesn't exist. So I did: >> >> aSixxShapeChangeStream shapeChangers at: #SmallDouble put: Float. >> But then, SIXX use Float >> readFrom: aStream >> "Answer a new Float as described on the stream, aStream." ^(super >> readFrom: aStream) asFloat >> >> >> So, of course " Float readFrom: '1.0000000000000000E-02' " -> 1.0 >> >> So my 0.01 in gemstone become 1.0 in Pharo.... >> >> Am I doing something wrong or this is expected? What is the best >> workaround? >> >> In GemStone I could print the SmallDouble in the XML with a method like >> >> Float >> xmlRepresentation >> ^ String streamContents: >> [:strm | self printOn: strm base: 10] >> >> Is this the correct approach? If true, I guess I should define: >> >> Float >> sixxContentOn: aStream indent: level context: dictionary aStream >> nextPutAll: self xmlRepresentation >> >> >> Thoughts? >> >> Thanks in advance, >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > >

Feb. 26, 2014

Re: [Pharo-dev] Floats problem with SIXX between Pharo and GemStone

by Nicolas Cellier

That's exactly for this kind of reasons that I developped an ExtendedNumberParser connected to Number class>>readFrom:, to allow a variety of formats used in the rest of the world. It would have been easy to allow upper letter exponents in this parser, but the class was considered superfluous and removed from Pharo 3.0... 2014-02-26 22:38 GMT+01:00 Mariano Martinez Peck <marianopeck(a)gmail.com>: > Hi guys, > > When I export SmallDoubles with SIXX in GemStone it generates something > like this: > > <sixx.object sixx.id="15" sixx.name="close" sixx.type="SmallDouble" > >1.0000000000000000E-02</sixx.object> > > This is because "0.01 asString" -> '1.0000000000000000E-02' > > Then I want to load this in Pharo. So first problem is that of course > SmallDouble doesn't exist. So I did: > > aSixxShapeChangeStream shapeChangers at: #SmallDouble put: Float. > But then, SIXX use Float >> readFrom: aStream > "Answer a new Float as described on the stream, aStream." ^(super > readFrom: aStream) asFloat > > > So, of course " Float readFrom: '1.0000000000000000E-02' " -> 1.0 > > So my 0.01 in gemstone become 1.0 in Pharo.... > > Am I doing something wrong or this is expected? What is the best > workaround? > > In GemStone I could print the SmallDouble in the XML with a method like > > Float >> xmlRepresentation > ^ String streamContents: > [:strm | self printOn: strm base: 10] > > Is this the correct approach? If true, I guess I should define: > > Float >> sixxContentOn: aStream indent: level context: dictionary aStream > nextPutAll: self xmlRepresentation > > > Thoughts? > > Thanks in advance, > > -- > Mariano > http://marianopeck.wordpress.com >

Feb. 26, 2014

Re: [Pharo-dev] about dateAndTime and TimeStamp

by Esteban A. Maringolo

I share the same idiomatic feeling with Norbert. However it is completely counter-intuitive (and counter productive too) that you can't instantiate a DateAndTime using the class side builder #date:time:, it is available in Pharo 2.0, but #date:time: was removed in a 3.0 image I tried a month ago. Regards! Esteban A. Maringolo 2014-02-26 17:36 GMT-03:00 Norbert Hartl <norbert(a)hartl.name>: > > Am 26.02.2014 um 21:29 schrieb Pharo4Stef <pharo4Stef(a)free.fr>: > >> one of these days we will have to remove TimeStamp because it just adds noise to the system (in fact I would not have any problem to see DateAndTime renamed as timestamp - but having the two for nothing looks useless to me). > > +100 > > I don't really get what the use of it is, too. The mere fact that DateAndTime printString returns ISO8601 dates and TimeStamp does not makes me always use DateAndTime instead. My problem is that I often take a "snapshot of time" (like in a log event) that for me as a non-native speaker is more related to the word timeStamp than DatenAndTime which sounds like a date and time management object. But everytime I write > > timeStamp := DateAndTime now > > it feels wrong. So I would be glad if there would be some clarification here. > > Norbert > > >

Feb. 26, 2014

Re: [Pharo-dev] How to upload some version from the package-cache to a StHub project

by MartinW

Gabriel Cotelli-3 wrote > I have a whole package history in my local package cache and I want to > upload it to a new SmalltalkHub project. I've tried using the Monticello > browser but it insists in creating a new version of the package when I do > the "Save" to the new repository. > > Is there some option to do something like this? Or some script? If you have several packages you can use this script: Gofer new package: 'MyProject-Core'; package: 'MyProject-Tests'; url: 'http://smalltalkhub.com/mc/USER/MyProject/main/' username: 'USER' password: '***'; push. (Thanks again to Camillo Bruni: http://stackoverflow.com/questions/17454965/how-to-copy-several-monticello-…) m. -- View this message in context: http://forum.world.st/How-to-upload-some-version-from-the-package-cache-to-… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Feb. 26, 2014

Re: [Pharo-dev] about dateAndTime and TimeStamp

by Sven Van Caekenberghe

Everything is ready to do just that, see https://pharo.fogbugz.com/f/cases/12197/should-remove-TimeStamp we just decided not to do the actual removal for 3.0 On 26 Feb 2014, at 21:29, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > one of these days we will have to remove TimeStamp because it just adds noise to the system (in fact I would not have any problem to see DateAndTime renamed as timestamp - but having the two for nothing looks useless to me). > > Stef

Feb. 26, 2014