- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Platform file encoding for FFI

by Alistair Grant

On Wed, 19 Sep 2018 at 10:26, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > On Tue, Sep 18, 2018 at 4:40 PM Alistair Grant <akgrant0710(a)gmail.com> wrote: >> >> I realise of course that this could all be done in FFI, and I agree with >> all Estaban's arguments in favour of FFI, my main motivation was that >> the code is already in the VM, and to avoid code duplication with the >> obvious benefit that if a bug is fixed it will apply everywhere. > > > Yeh. At the end it's a matter of debugging cycles. > Imagine making the "compile-restart" steps that you're facing while changing the plugin almost negligible in the "change-compile-restart-test" loop :). This is true if the code only resides in the image, but in this case the code won't be going away from the VM any time soon. Anyway, for whoever does implement the code for FFI the option is always there. Thanks to everyone for their replies! Cheers, Alistair

Sept. 19, 2018

[Pharo 7.0-dev] Build #1259: 21660-Changing-the-superclass-of-a-Class-using-superclass-method-does-not-update-instSize-correctly

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1259 was: FAILURE. The Pull Request #1618 was integrated: "21660-Changing-the-superclass-of-a-Class-using-superclass-method-does-not-update-instSize-correctly" Pull request url: https://github.com/pharo-project/pharo/pull/1618 Issue Url: https://pharo.fogbugz.com/f/cases/21660 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 19, 2018

[Pharo 7.0-dev] Build #1258: 22457-Provide-a-CalendarPresenter-fully-written-in-Spec

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1258 was: SUCCESS. The Pull Request #1804 was integrated: "22457-Provide-a-CalendarPresenter-fully-written-in-Spec" Pull request url: https://github.com/pharo-project/pharo/pull/1804 Issue Url: https://pharo.fogbugz.com/f/cases/22457 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 19, 2018

Re: [Pharo-dev] Pharo Downloads are sluggish

by Esteban A. Maringolo

Hi Marcus, Thank you. Anybody WILLING to use it will wait whatever it takes, but my concern, and rant, is about these that want to give it a try and will abort it even before running it. I'm happily using Pharo in Windows preparing it for a demo I'll be making. Regards! On 19/09/2018 10:06, Marcus Denker wrote: > I will have a look how to improve the situation. > > (I hope to be able to do it by next week). > > Marcus > >> On 19 Sep 2018, at 02:10, Esteban Maringolo <emaringolo(a)gmail.com >> <mailto:emaringolo@gmail.com>> wrote: >> >> After sending the previous email I checked the progress and it was >> aborted due to a network error. >> >> <pharo-cancelled.PNG> >> >> I retried and apparently the speed got to a more reasonable one, with >> peaks of 300KB/sec. >> >> <pharo-retry.png> >> >> >> My guess is that the bottleneck is at where the files are hosted, and >> if you attempt to download while maybe there are several CI builds >> running or something else is using the fileserver bandwidth, then it >> impacts the overall download speed of those attempting to download >> just the basic elements. >> >> Regards! >> >> Esteban A. Maringolo >> >> >> El mar., 18 sept. 2018 a las 21:03, Esteban Maringolo >> (<emaringolo(a)gmail.com <mailto:emaringolo@gmail.com>>) escribiÃ³: >> >> Is there a reason why the latest version of the builds linked from >> the website are not hosted in some CDN, Amazon S3 or similar? >> >> Maybe in Europe the speed is fast, but where I am (Argentina) it >> is really slow, the screenshot shows 3.5KB/s, it averages 10KB/s, >> with peaks of 40KB/s. >> >> This is an pitiful boarding experience, that will make many cancel >> it even before getting to open the downloaded launcher. >> >> <node-pharo.png> >> >> The screenshot shows that is not a problem with my home >> connection, which isn't the fastest but is "normal" for my use cases. >> >> Regards, >> >> Esteban A. Maringolo >> >> ps: When I finished writing this email, this was the progress... >> <image.png> >> > -- Esteban A. Maringolo

Sept. 19, 2018

Re: [Pharo-dev] Pharo Downloads are sluggish

by Marcus Denker

I will have a look how to improve the situation. (I hope to be able to do it by next week). Marcus > On 19 Sep 2018, at 02:10, Esteban Maringolo <emaringolo(a)gmail.com> wrote: > > After sending the previous email I checked the progress and it was aborted due to a network error. > > <pharo-cancelled.PNG> > > I retried and apparently the speed got to a more reasonable one, with peaks of 300KB/sec. > > <pharo-retry.png> > > > My guess is that the bottleneck is at where the files are hosted, and if you attempt to download while maybe there are several CI builds running or something else is using the fileserver bandwidth, then it impacts the overall download speed of those attempting to download just the basic elements. > > Regards! > > Esteban A. Maringolo > > > El mar., 18 sept. 2018 a las 21:03, Esteban Maringolo (<emaringolo(a)gmail.com <mailto:emaringolo@gmail.com>>) escribiÃ³: > Is there a reason why the latest version of the builds linked from the website are not hosted in some CDN, Amazon S3 or similar? > > Maybe in Europe the speed is fast, but where I am (Argentina) it is really slow, the screenshot shows 3.5KB/s, it averages 10KB/s, with peaks of 40KB/s. > > This is an pitiful boarding experience, that will make many cancel it even before getting to open the downloaded launcher. > > <node-pharo.png> > > The screenshot shows that is not a problem with my home connection, which isn't the fastest but is "normal" for my use cases. > > Regards, > > Esteban A. Maringolo > > ps: When I finished writing this email, this was the progress... > <image.png>

Sept. 19, 2018

[Pharo 7.0-dev] Build #1257: 22469-Small-cleanup-in-NEC-Model-classes

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1257 was: FAILURE. The Pull Request #1815 was integrated: "22469-Small-cleanup-in-NEC-Model-classes" Pull request url: https://github.com/pharo-project/pharo/pull/1815 Issue Url: https://pharo.fogbugz.com/f/cases/22469 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 19, 2018

[Pharo 7.0-dev] Build #1256: 22448 Cleanup ManifestSystemModel and related package

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1256 was: FAILURE. The Pull Request #1796 was integrated: "22448 Cleanup ManifestSystemModel and related package" Pull request url: https://github.com/pharo-project/pharo/pull/1796 Issue Url: https://pharo.fogbugz.com/f/cases/22448 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 19, 2018

Re: [Pharo-dev] Fraction and ScaledDecimal should be not be serialized as Float in STON format

by Julien

Sept. 19, 2018

Re: [Pharo-dev] Platform file encoding for FFI

by Guillermo Polito

On Tue, Sep 18, 2018 at 4:40 PM Alistair Grant <akgrant0710(a)gmail.com> wrote: > > I haven't looked at using FFI much, however it is easy to imagine > that > > different file encoding rules on different platforms will make > writing > > FFI calls more difficult, > > > > Well not really (from my point of view :)) > > From the point of view of the FFI call an encoded string is just a bunch > of > > bytes. FFI does not do any interpretation of them. > > Right, but getting the appropriately encoded bunch of bytes is the issue. > :-) > > Yes, the thing is that this would require some new extensions in uFFI to support encodings. The good point of that is that that would have a positive impact in ***ALL** FFI bindings using strings (by making explicit to people that they should care about encodings :)). > > Maybe... Are the OSX routines exposed as C functions (that we can call > through > > FFI) or they are objective-C methods/functions (that are more > complicated to > > map)? > > The OSX routines are exposed as C functions (and available as > Objective-C methods), see convertChars() in > platforms/unix/vm/sqUnixCharConv.c. > Nice! On Tue, Sep 18, 2018 at 11:21:41AM +0200, Esteban Lorenzano wrote: > > > self > > > ffiCall: #(bool saveContentsToFile(String fileName, String > contents)) > > > options: #(+stringEncodings( fileName return , platformAPI contents) > > > > This is cool. > > What I do not like is to rely on primitives to do that encoding. > > This should be in image??? using FFI if needed (this is all because we > > want to rely less and less on plugins :P) > > I realise of course that this could all be done in FFI, and I agree with > all Estaban's arguments in favour of FFI, my main motivation was that > the code is already in the VM, and to avoid code duplication with the > obvious benefit that if a bug is fixed it will apply everywhere. Yeh. At the end it's a matter of debugging cycles. Imagine making the "compile-restart" steps that you're facing while changing the plugin almost negligible in the "change-compile-restart-test" loop :).

Sept. 19, 2018

Re: [Pharo-dev] [rmod] Float should not implement #to:, #to:by:, etc...

by Davide Grandi

> 0.0 to: 1.0 by: 0.1 Receiver and arguments, lexically (the dot), are float BUT are written as decimal number (zero, one, one tenth). I think that in a text you can ONLY write "decimal" numbers or (in bases other than 10 [or with factors other than 2^x and 5 ?]), at worst, repeating decimals (eg 0,1 in base 3 = 1/3 ~ 0.333...), that are ultimately fractions. So, may be, if the receiver or an argument is a float the compiler may issue a warning and compile to non-float, if receiver or arguments are computed ... there should be a default behaviour. Best regards, Â Â Davide Grandi (PS : I work mainly in an ERP that has only integers ... and doubles) On 18/09/2018 11:52, Guillaume Larcheveque wrote: > Maybe #to:by: should convert its parameters in Fraction to avoid > Floats problems (not sure, just an idea) > > 2018-09-18 11:25 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com > <mailto:estebanlm@gmail.com>>: > > >> On 18 Sep 2018, at 11:13, Guillermo Polito >> <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>> wrote: >> >> >> >> On Tue, Sep 18, 2018 at 11:06 AM Julien >> <julien.delplanque(a)inria.fr <mailto:julien.delplanque@inria.fr>> >> wrote: >> >> Hello, >> >> I realised that it is possible to create an interval of floats. >> >> I think this is bad because, since intervals are computed by >> successively adding a number, it might result in precision >> errors. >> >> (0.0 to: 1.0 by: 0.1) asArray >>> #(0.0 0.1 0.2 >> 0.30000000000000004 0.4 0.5 0.6000000000000001 >> 0.7000000000000001 0.8 0.9 1.0) >> >> The correct (precise) way to do it would be to use ScaledDecimal: >> >> (0.0s1 to: 1.0s1 by: 0.1s1) asArray >>> #(0.0s1 0.1s1 0.2s1 >> 0.3s1 0.4s1 0.5s1 0.6s1 0.7s1 0.8s1 0.9s1 1.0s1) >> >> I opened an issue about it: >> https://pharo.fogbugz.com/f/cases/22467/Float-should-not-implement-to-to-by… >> <https://pharo.fogbugz.com/f/cases/22467/Float-should-not-implement-to-to-by…> >> >> And Iâd like to discuss this with you. >> >> What do you think? >> >> >> Well, I think it's a matter of balance :) >> >> #to:by: is defined in Number. So we could, for example, cancel it >> in Float. >> However, people would still be able to do >> >> 1 to: 1.0 by: 0.1 >> >> Which would still show problems. > > Nevertheless, I have seen this a lot of times. > > 0.0 to: 1.0 by: 0.1 > > Is a common use case. > >> >> And moreover, we could try to do >> >> 1 to: 7 by: (Margin fromNumber: 1) >> >> And even worse >> >> 1 to: Object new by: (Margin fromNumber: 1) >> >> I think adding type-validations all over the place is not a good >> solution, and is kind of opposite to our philosophy... >> >> So we should >> Â - document the good usages >> Â - document the bad ones >> Â - and live with the fact that we have a relaxed type system that >> will fail at runtime :) > > yup. > But not cancel. > > Esteban > >> >> Guille > > > > > -- > *Guillaume Larcheveque* >

Sept. 19, 2018