- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core] 7a9bfe: 60269

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 7a9bfe6726dd3b686f6cd3329f4afd61f2b704d2 https://github.com/pharo-project/pharo-core/commit/7a9bfe6726dd3b686f6cd332… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-10-26 (Wed, 26 Oct 2016) Changed paths: A Kernel-Tests.package/ProcessTest.class/instance/testing/testInjectingExceptionHandlerIntoProcessWithArg.st M Rubric.package/RubCharacterScanner.class/instance/scanning/basicScanCharactersFrom_to_in_rightX_stopConditions_kern_.st M SUnit-Core.package/TestExecutionEnvironment.class/instance/controlling/prepareForNewProcess_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60268.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60269.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60268.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60269.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60269 18351 Inspector goes CPU bound displaying some large Text https://pharo.fogbugz.com/f/cases/18351 19224 TestExecutionEnvironment should use Process ondo to insert default error handler https://pharo.fogbugz.com/f/cases/19224 http://files.pharo.org/image/60/60269.zip

Oct. 26, 2016

Re: [Pharo-dev] How to try Bloc?

by Denis Kudriashov

2016-10-26 10:40 GMT+02:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > > Do you have instructions how to run it? > And if you have one please put also instruction for Brick.

Oct. 26, 2016

Re: [Pharo-dev] [Bloc] Hierarchy of BiEvent

by Tudor Girba

Hi Denis, Thanks a lot for looking at this! I will let Glenn answer. Cheers, Doru > On Oct 26, 2016, at 11:02 AM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > Hi. > > I look at dev version of Bloc and have questions about events. > > There is duplicated hierarchy of OSEvent and BlEvent. For example for OSKeyDownEvent and OSMouseButtonPressEvent > there are same events from Block: BlKeyDownEvent and BlMouseDownEvent. > > Bloc of course add many new events like BlDragEvent and BlDblClickEvent. > But why we not manage all events equally? why we need this distinction? > > Also I was so much surprized about keyboard modifiers. In OS there is OSStateModifiers with smart boolean states like leftShiftPressed, leftAltPressed which are decoded from integer bits of raw SDL event. > > And in Bloc it is BlKeyModifiers which are created from OSStateModifier. And here is most amazing thing: BlKeyModifiers encode smart boolean flags about keys back into integer bits. So we have: > > SDL event int => OSStateModifiers booleans => BlKeyModifiers int > > Why it is done like this? > And currently BlKeyModifiers lost many states from OSStateModifiers. -- www.tudorgirba.com www.feenk.com "Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."

Oct. 26, 2016

Re: [Pharo-dev] How to try Bloc?

by Dimitris Chloupis

No idea how you managed to install it, it gives me a missing ' error same setup, macos sierra, pharo 6 latest ConfigurationOfBloc (Pharo/Bloc repo) loadDevelopment On Wed, Oct 26, 2016 at 11:42 AM Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Hi > > I tried image from CI (both stable and dev) and I tried version by loading > config in latest Pharo 6. > Both are not working for me. I run basicExamples: > > - ci version said that this is some nil object inside > > - config version just crashed. > > > Do you have instructions how to run it? > > I tried it on Sierra Mac. > > Best regards, > Denis >

Oct. 26, 2016

[Bloc] Hierarchy of BiEvent

by Denis Kudriashov

Hi. I look at dev version of Bloc and have questions about events. There is duplicated hierarchy of OSEvent and BlEvent. For example for OSKeyDownEvent and OSMouseButtonPressEvent there are same events from Block: BlKeyDownEvent and BlMouseDownEvent. Bloc of course add many new events like BlDragEvent and BlDblClickEvent. But why we not manage all events equally? why we need this distinction? Also I was so much surprized about keyboard modifiers. In OS there is OSStateModifiers with smart boolean states like leftShiftPressed, leftAltPressed which are decoded from integer bits of raw SDL event. And in Bloc it is BlKeyModifiers which are created from OSStateModifier. And here is most amazing thing: BlKeyModifiers encode smart boolean flags about keys back into integer bits. So we have: SDL event int => OSStateModifiers booleans => BlKeyModifiers int Why it is done like this? And currently BlKeyModifiers lost many states from OSStateModifiers.

Oct. 26, 2016

Re: [Pharo-dev] roundTo: strange behavior

by ClÃ©ment Bera

I think the right way to solve these issues is not to think about it like a Math problem. We need to write tests showing bugs and doing lots of coverage. Then, we can look into other programming languages (Java, Ruby, Python, etc), port an implementation and ensure it's correct. This is the kind of things where people have spent days to get right and efficient. The goal is not to figure how to do it better but how to port the best implementation out there. On Wed, Oct 26, 2016 at 9:58 AM, Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com> wrote: > > > 2016-10-26 9:14 GMT+02:00 stepharo <stepharo(a)free.fr>: > >> Hi nicolas >> >> So what is the solution? We can integrate fast a solution. >> I would really like to see them fix in Pharo 60. >> I'm writing a book for newbie and this is the third time I change one >> chapter >> so may be I should stop and throw away this chapter. >> >> > 1) for Fraction: > > round: numberOfWishedDecimal > v := 10 raisedTo: numberOfWishedDecimal. > ^ ((self * v) rounded / v) asFloat > > or just replace asFloat if you wish to remain exact: > > round: numberOfWishedDecimal > v := 10 raisedTo: numberOfWishedDecimal. > ^ ((self * v) rounded / v) asScaledDecimal: numberOfWishedDecimal > > 2) for Float, it is in 15471: > > round: numberOfWishedDecimal > | v maxNumberOfDecimals | > maxNumberOfDecimals := self class precision - 1 - (self exponent max: > self class emin). > maxNumberOfDecimals < numberOfWishedDecimal ifTrue: [^self]. > v := 10 raisedTo: numberOfWishedDecimal. > ^ ((self asFraction * v) rounded / v) asFloat > > or if Fraction already answers a Float: > > round: numberOfWishedDecimal > | maxNumberOfDecimals | > maxNumberOfDecimals := self class precision - 1 - (self exponent max: > self class emin). > maxNumberOfDecimals < numberOfWishedDecimal ifTrue: [^self]. > ^ self asFraction round: numberOfWishedDecimal > > It's slower than current implementation, but will round exactly to the > nearest Float. > It's possible to have faster implementation up to 22 decimals if you > provide a fused-multiply-accumulate primitive... > > > You see I'm not good in math so even if I try hard I will not have a good >> solution. >> This is the same for marcus and most people in our team. >> I reopened these issues. >> >> Stef >> >> >> >> 2016-10-25 23:22 GMT+02:00 stepharo <stepharo(a)free.fr>: >> >>> Ok for the advice >>> >>> Now round: aNumberOfDigits seems to work fine. >>> >>> Stef >>> >>> >> No it's not, but issues are timing out too fast ;) >> https://pharo.fogbugz.com/f/cases/15471/Can-t-round-Float-fm >> ax-to-2-decimal-places >> https://pharo.fogbugz.com/f/cases/15472/Fraction-rounding-to >> -n-decimal-places-is-inexact >> https://pharo.fogbugz.com/f/cases/15473/Float-round-to-n-dec >> imal-places-is-not-in-agreement-with-printShowingDecimalPlaces >> >> I hate to say that, but try in python, they got it right... >> >> >> >>> Le 25/10/16 Ã 11:05, Henrik Johansen a Ã©crit : >>> >>> +1. >>> >>> Unless you're dealing with fixed precision* entities, it's usually >>> better to specify digits to display in printing methods themselves >>> (#printShowingDecimalPlaces: & friends in base image). >>> As per previous discussions around this that arise every second year or >>> so, rounding the number itself (as long as we're dealing with floats) will >>> never work as you want reliably. >>> >>> Cheers, >>> Henry >>> >>> * And in that case, you'd use ScaledDecimals >>> >>> On 23 Oct 2016, at 7:08 , phil(a)highoctane.be wrote: >>> >>> I use the Printf package for that. >>> >>> v := 65.456. >>> 'With 2 decimal digits: %5.2f, or 3 like this: %6.3f' >>> printf: {v. v}. >>> >>> With 2 decimal digits: 65.45, or 3 like this: 65.456 >>> >>> It is in http://www.smalltalkhub.com/#!/~philippeback/HOExtras >>> >>> Printf >>> >>> I am just used to C printf and well, I like the way it works. >>> >>> Phil >>> >>> >>> >> >> >

Oct. 26, 2016

How to try Bloc?

by Denis Kudriashov

Hi I tried image from CI (both stable and dev) and I tried version by loading config in latest Pharo 6. Both are not working for me. I run basicExamples: - ci version said that this is some nil object inside - config version just crashed. Do you have instructions how to run it? I tried it on Sierra Mac. Best regards, Denis

Oct. 26, 2016

Re: [Pharo-dev] roundTo: strange behavior

by Nicolas Cellier

2016-10-26 9:14 GMT+02:00 stepharo <stepharo(a)free.fr>: > Hi nicolas > > So what is the solution? We can integrate fast a solution. > I would really like to see them fix in Pharo 60. > I'm writing a book for newbie and this is the third time I change one > chapter > so may be I should stop and throw away this chapter. > > 1) for Fraction: round: numberOfWishedDecimal v := 10 raisedTo: numberOfWishedDecimal. ^ ((self * v) rounded / v) asFloat or just replace asFloat if you wish to remain exact: round: numberOfWishedDecimal v := 10 raisedTo: numberOfWishedDecimal. ^ ((self * v) rounded / v) asScaledDecimal: numberOfWishedDecimal 2) for Float, it is in 15471: round: numberOfWishedDecimal | v maxNumberOfDecimals | maxNumberOfDecimals := self class precision - 1 - (self exponent max: self class emin). maxNumberOfDecimals < numberOfWishedDecimal ifTrue: [^self]. v := 10 raisedTo: numberOfWishedDecimal. ^ ((self asFraction * v) rounded / v) asFloat or if Fraction already answers a Float: round: numberOfWishedDecimal | maxNumberOfDecimals | maxNumberOfDecimals := self class precision - 1 - (self exponent max: self class emin). maxNumberOfDecimals < numberOfWishedDecimal ifTrue: [^self]. ^ self asFraction round: numberOfWishedDecimal It's slower than current implementation, but will round exactly to the nearest Float. It's possible to have faster implementation up to 22 decimals if you provide a fused-multiply-accumulate primitive... You see I'm not good in math so even if I try hard I will not have a good > solution. > This is the same for marcus and most people in our team. > I reopened these issues. > > Stef > > > > 2016-10-25 23:22 GMT+02:00 stepharo <stepharo(a)free.fr>: > >> Ok for the advice >> >> Now round: aNumberOfDigits seems to work fine. >> >> Stef >> >> > No it's not, but issues are timing out too fast ;) > https://pharo.fogbugz.com/f/cases/15471/Can-t-round-Float- > fmax-to-2-decimal-places > https://pharo.fogbugz.com/f/cases/15472/Fraction-rounding- > to-n-decimal-places-is-inexact > https://pharo.fogbugz.com/f/cases/15473/Float-round-to-n- > decimal-places-is-not-in-agreement-with-printShowingDecimalPlaces > > I hate to say that, but try in python, they got it right... > > > >> Le 25/10/16 Ã 11:05, Henrik Johansen a Ã©crit : >> >> +1. >> >> Unless you're dealing with fixed precision* entities, it's usually better >> to specify digits to display in printing methods themselves >> (#printShowingDecimalPlaces: & friends in base image). >> As per previous discussions around this that arise every second year or >> so, rounding the number itself (as long as we're dealing with floats) will >> never work as you want reliably. >> >> Cheers, >> Henry >> >> * And in that case, you'd use ScaledDecimals >> >> On 23 Oct 2016, at 7:08 , phil(a)highoctane.be wrote: >> >> I use the Printf package for that. >> >> v := 65.456. >> 'With 2 decimal digits: %5.2f, or 3 like this: %6.3f' >> printf: {v. v}. >> >> With 2 decimal digits: 65.45, or 3 like this: 65.456 >> >> It is in http://www.smalltalkhub.com/#!/~philippeback/HOExtras >> >> Printf >> >> I am just used to C printf and well, I like the way it works. >> >> Phil >> >> >> > >

Oct. 26, 2016

Re: [Pharo-dev] roundTo: strange behavior

by stepharo

Hi nicolas So what is the solution? We can integrate fast a solution. I would really like to see them fix in Pharo 60. I'm writing a book for newbie and this is the third time I change one chapter so may be I should stop and throw away this chapter. You see I'm not good in math so even if I try hard I will not have a good solution. This is the same for marcus and most people in our team. I reopened these issues. Stef > > > 2016-10-25 23:22 GMT+02:00 stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>>: > > Ok for the advice > > Now round: aNumberOfDigits seems to work fine. > > Stef > > > > No it's not, but issues are timing out too fast ;) > https://pharo.fogbugz.com/f/cases/15471/Can-t-round-Float-fmax-to-2-decimal… > https://pharo.fogbugz.com/f/cases/15472/Fraction-rounding-to-n-decimal-plac… > https://pharo.fogbugz.com/f/cases/15473/Float-round-to-n-decimal-places-is-… > > I hate to say that, but try in python, they got it right... > > > Le 25/10/16 Ã 11:05, Henrik Johansen a Ã©crit : >> +1. >> >> Unless you're dealing with fixed precision* entities, it's >> usually better to specify digits to display in printing methods >> themselves (#printShowingDecimalPlaces: & friends in base image). >> As per previous discussions around this that arise every second >> year or so, rounding the number itself (as long as we're dealing >> with floats) will never work as you want reliably. >> >> Cheers, >> Henry >> >> * And in that case, you'd use ScaledDecimals >> >>> On 23 Oct 2016, at 7:08 , phil(a)highoctane.be >>> <mailto:phil@highoctane.be> wrote: >>> >>> I use the Printf package for that. >>> >>> v := 65.456. >>> 'With 2 decimal digits: %5.2f, or 3 like this: %6.3f' >>> printf: {v. v}. >>> >>> With 2 decimal digits: 65.45, or 3 like this: 65.456 >>> >>> It is in http://www.smalltalkhub.com/#!/~philippeback/HOExtras >>> <http://www.smalltalkhub.com/#%21/%7Ephilippeback/HOExtras> >>> >>> Printf >>> >>> I am just used to C printf and well, I like the way it works. >>> >>> Phil > >

Oct. 26, 2016

Re: [Pharo-dev] [Ann] Stack Android VM

by stepharo

I want to thank Inria to have listen to me (and it was not that simple) to let Santiago work on that. So please use it and show us that you use it. Stef Le 23/10/16 Ã 22:03, Santiago Bragagnolo a Ã©crit : > Still far from production. But since i would happy to have some > feedback, I'm happy to show you some progress on the android VM. Not > yet release. But we have already a way of compiling and deploying an > image into an android device. > > You can check it in this repo github. > https://github.com/sbragagnolo/pharo-vm/ > > The building steps are detailed on the README-Android.md file. > > > Building the Stack AndroidVM > > 1. > > Download the sources fromgithub > <https://github.com/sbragagnolo/pharo-vm> > > git clone --depth=1https://github.com/sbragagnolo/pharo-vm > cd pharo-vm > 2. > > Set-up your environment: This script will download the SDK > installer and NDK R10 > > cd android/scripts > ./setupAndroidEnvironment.st > > This script downloads the content from > > * 'http://dl.google.com/android/repository/android-ndk-r10e-linux-x86_64.zip'. > * 'http://dl.google.com/android/android-sdk_r24.4.1-linux.tgz'. > > After this process you should have available the environment > variables ANDROID_NDK_HOME and ANDROID_SDK_HOME. Ensure this by > checking your .bashrc file at the user's home directory. > > 3. > > Create a new image: this image will be created by pointing to this > local git repository > > cd android/scripts > ./newImage.st > 4. > > Link sources to the build folder: The Android vm relies on a Java > wrapper. This sources must be accessible from the build folder. > > cd android/scripts > ./linkSources.st > 5. > > Generate the sources of the stack vm: This script executes the > generator of the image created on int the 3rd step. > > cd android/scripts > ./generateStackAndroidMake.st > 6. > > Generate the resource image for deployment: This script download > and suites up an image for deployment on the folder > build/assets/SmalltalkRessources > > cd android/scripts > ./newResourceImage.st > > This image created in this point is downloaded with it related VM > for editing and loading the code you want to deploy, or configure > the things you want. > > 7. > > The VM compilation: This script generates the libraries with the > VM code. > > cd build > ./build.sh > 8. > > The Java wrapper compilation and Android Application packaging > > cd build > ./package.sh > 9. > > Installing into your device. If you want to generate an APK file > with your custom name, you will need to deal with the > AndroidManifest.xml before runing the package.sh script :) > > cd build/bin > adb install -r StackActivity-debug.apk > > > - Im currently working on the JIT version of the VM, that still > avoiding me :). > But you have as well the instruction on the same README-Android.me file. > > > Santiago > > > > > >

Oct. 26, 2016