- Pharo-users - lists.pharo.org

Re: [Pharo-users] UTF-8 encoding

by Sven Van Caekenberghe

> On 16 Apr 2018, at 17:06, Benoit St-Jean via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > > From: Benoit St-Jean <bstjean(a)yahoo.com> > Subject: UTF-8 encoding > Date: 16 April 2018 at 17:06:28 GMT+2 > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Reply-To: Benoit St-Jean <bstjean(a)yahoo.com> > > > Regarding the problems I have with my firstname and file paths and utf-8 encoding, I found something weird in the UTF-8 encoding. In fact, to be more precise, I found something strange when converting a String to a ByteArray (which UTF-8 encoders convert from) > > If I look at the example in the comment of ByteArray>>utf8Decoded, 'Les Ã©lÃ¨ves franÃ§ais' is encoded as: > > #[76 101 115 32 195 169 108 195 168 118 101 115 32 102 114 97 110 195 167 97 105 115] > > NOW, if I take that very same string, 'Les Ã©lÃ¨ves franÃ§ais' , and convert it to a ByteArray, I get : > 'Les Ã©lÃ¨ves franÃ§ais' asByteArray printString. You cannot do that, that is using a null encoding, which is almost always wrong. Please read (the first part) of https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… carefully. > #[76 101 115 32 233 108 232 118 101 115 32 102 114 97 110 231 97 105 115] > > The 2 don't match! > > By the way, this problem exists on Pharo 5.1, 6.1 and 7.1 (on Windows 10 ) > > Can anyone confirm/infirm on another platform to see if this is Windows-specific? This behaviour is not-windows specific, it is like that on all platforms, and it is correct ;-) > ----------------- > BenoÃ®t St-Jean > Yahoo! Messenger: bstjean > Twitter: @BenLeChialeux > Pinterest: benoitstjean > Instagram: Chef_Benito > IRC: lamneth > Blogue: endormitoire.wordpress.com > "A standpoint is an intellectual horizon of radius zero". (A. Einstein) > >

April 16, 2018

UTF-8 encoding

by Benoit St-Jean

Regarding the problems I have with my firstname and file paths and utf-8 encoding, I found something weird in the UTF-8 encoding.Â In fact, to be more precise, I found something strange when converting a String to a ByteArray (which UTF-8 encoders convert from) If I look at the example in the comment of ByteArray>>utf8Decoded, 'Les Ã©lÃ¨ves franÃ§ais' is encoded as: #[76 101 115 32 195 169 108 195 168 118 101 115 32 102 114 97 110 195 167 97 105 115] NOW, if I take that very same string, 'Les Ã©lÃ¨ves franÃ§ais' , and convert it to a ByteArray, I get : 'Les Ã©lÃ¨ves franÃ§ais' asByteArray printString. #[76 101 115 32 233 108 232 118 101 115 32 102 114 97 110 231 97 105 115] The 2 don't match! By the way, this problem exists on Pharo 5.1, 6.1 and 7.1 (on Windows 10 ) Can anyone confirm/infirm on another platform to see if this is Windows-specific? ----------------- BenoÃ®t St-Jean Yahoo! Messenger: bstjean Twitter: @BenLeChialeux Pinterest: benoitstjean Instagram: Chef_Benito IRC: lamneth Blogue: endormitoire.wordpress.com "A standpoint is an intellectual horizon of radius zero".Â (A. Einstein)

April 16, 2018

Re: [Pharo-users] Some random musings

by Benoit St-Jean

"Float randomBetween: -4.1 and: 2.5 would be the most descriptive and compliant to your signature ;-)" I also prefer #randomBetween:and: . "Going to the class side of Float makes sense because you create a new instance." But I'm not so sure about putting this on the class side. In fact, right now #atRandom is on the instance side and it's been that way since the beginning.Â It would be akward to have one method of generating random numbers on the class side and all others on the instance side.Â And moving everything on the class side would break tons of code and legacy code.Â Besides, random numbers have always been seen and/or dealt with as streams : the intent was to get "the next one" in the stream, not create "a new instance" ----------------- BenoÃ®t St-Jean Yahoo! Messenger: bstjean Twitter: @BenLeChialeux Pinterest: benoitstjean Instagram: Chef_Benito IRC: lamneth Blogue: endormitoire.wordpress.com "A standpoint is an intellectual horizon of radius zero".Â (A. Einstein)

April 16, 2018

Re: [Pharo-users] Some random musings

by Benoit St-Jean

"Any interest to introduce a method to produce random float numbers in an interval in Pharo ?" Yes, that would definitely be useful !!!!Â And it would not only be useful for Float but for all numbers.Â Would save us from the usual "#truncated and +1" trick we always have to write!! ----------------- BenoÃ®t St-Jean Yahoo! Messenger: bstjean Twitter: @BenLeChialeux Pinterest: benoitstjean Instagram: Chef_Benito IRC: lamneth Blogue: endormitoire.wordpress.com "A standpoint is an intellectual horizon of radius zero".Â (A. Einstein)

April 16, 2018

[Pharo-Launcher] call for tests on Windows

by Christophe Demarey

Hi, Regarding the various problems Pharo Launchers had on Windows, we worked on a new installer based on Advanced Installer [1] to avoid UAC (User Account Control) and write permissions problems. This new installer now installs Pharo Launcher in the userâs local app data folder (where for sure, he has write permissions). Pharo Launcher also now have its own icon and use its own name instead of Pharo. Also, the uninstaller now works as expected. Last but not least, the installer is now signed to avoid warning of Windows Defender. Thanks to Ben Coman who did the first version of the packaging using Advanced Installer (was NSIS). This version should also improve the launch of Pharo images on Windows. So, please could you install and test this new version: and report any problem with it? http://files.pharo.org/pharo-launcher/win-alpha/ We do not have windows users around so itâs hard to know if it works outside our tests boxes. Thanks, Christophe [1] https://www.advancedinstaller.com/

April 16, 2018

Re: [Pharo-users] Where do we go now ?

by Jimmie Houchin

On 04/13/2018 07:33 AM, Esteban Lorenzano wrote: > > >> On 13 Apr 2018, at 14:23, Ben Coman <btc(a)openinworld.com >> <mailto:btc@openinworld.com>> wrote: >> >> Unfortunately there probably isn't one list. >> Its hard to unlearn what is accumulated >> and easy to take for granted what we know is obvious to everyone. >> Maybe we need a "Glossary" at >> https://github.com/pharo-project/pharo/tree/master/wiki >> where newcomers can add items for others to fill in. > > this is part a debate Stef and I have since years. > I think we need to put generic names to our tools: > > - System browser > - Source Version Control > - etc. > > while Stef supports fantasy names: > > - Calypso > - Iceberg > - etc. > > you know who won this debate ;) > > but at least I would like to add an option for special menu to show > what is suck tool. > > cheers, > Esteban Personally I have wished for a long time that Pharo used standard names for the default tools or libraries in the image. I think the fancy names can lead to confusion as to what am I supposed to use. Which one is the default one, which one is the development one. One shouldn't have to ask the mailing list to determine such things. If one plans on developing in Pharo for years or for decades. The constant turnover of names makes things cognitively more challenging and I would think it would also make bringing older code forward more difficult. I ask these questions as one who doesn't know the answer, but only has an opinion. This is not what I do everyday. What works best for the long view of our system? At some point we knowÂ the constant churn will be reduced and we will have a clean, as small as reasonable and stable system. When this is the case, what is best for Pharo in naming of tools and libraries? New names every time implementation changes? Or stable common understandable names, names which represent what the class is? I think the fancy name is okay for the development version. And when upgraded to becoming the default, the name becomes the default name. I think it would be nice to have stable names which can provide a stable api of class names and public messages which can be around for decades. I think innovation and creativity belong in better places than what's the new name for the System Browser, etc. It seems this would be nicer on us bears of very little brain. :) Jimmie

April 16, 2018

Re: [Pharo-users] Some random musings

by Sven Van Caekenberghe

#between:and: is a well known test selector, which is inclusive on both ends. > On 16 Apr 2018, at 12:59, jtuchel(a)objektfabrik.de wrote: > > Sven, Serge, > > Especially in the case of Floats, I think between:and: is *not* a good name. > As always, the question is if between:and: is exclusive or inclusive of the border values... So I think the better name is from:to:. I think this name indicates it includes the border values. > > Joachim > > > > > Am 16.04.18 um 12:51 schrieb Sven Van Caekenberghe: >> I think >> >> Float randomFrom: -4.1 to: 2.5 >> >> or >> >> Float randomBetween: -4.1 and: 2.5 >> >> would be the most descriptive and compliant to your signature ;-) >> >> An interval does not necessarily contain Floats. >> Going to the class side of Float makes sense because you create a new instance. >> >>> On 16 Apr 2018, at 11:51, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: >>> >>> Hi Pharoers, >>> >>> some random musings about Random numbers :-) >>> >>> In the context of the CORMAS project: >>> http://cormas.cirad.fr/indexeng.htm >>> I would like to propose an API for manipulating random numbers >>> to users who are not developers but modelers of complex systems. >>> >>> In CORMAS, people need to generate a lot of random numbers for simulation for exemple. For example, you can do: >>> >>> Cormas randomFloatFrom: -4.1 to: 2.5 >>> >>> âAt the moment, there is no Pharo API to generate with a one-liner a random float number between two values for example. >>> >>> You can do this for integers: 10 atRandom to generate an integer between 1 to 10. >>> >>> There is atRandom defined on Interval, so can you say : >>> (2.3 to: 4.5) atRandom >>> but it will not generate a random float numbers between 2.3 and 4.5 >>> >>> but numbers like: 2.3, 3.3 or 4.3. >>> because Interval are considered as a Collection. >>> >>> âAny comments about that ? >>> How we can enhance the situation ?â >>> Any interest to introduce a method to produce random float numbers in an interval in Pharo ? >>> >>> âThank youâ >>> -- >>> Serge Stinckwich >>> UMI UMMISCO 209 (SU/IRD/UY1) >>> "Programs must be written for people to read, and only incidentally for machines to execute." >>> http://www.doesnotunderstand.org/ >> >> > > -- > ----------------------------------------------------------------------- > Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de > Fliederweg 1 http://www.objektfabrik.de > D-71640 Ludwigsburg http://joachimtuchel.wordpress.com > Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1 > >

April 16, 2018

Re: [Pharo-users] Some random musings

by Sven Van Caekenberghe

> On 16 Apr 2018, at 12:57, Julien <julien.delplanque(a)inria.fr> wrote: > > Hello, > > Then this should be added to Integer class as well no? > > So the API is uniform. Probably yes. > Because, if I am not wrong, for now if you want to generate an integer that could be negative you have to use an Interval > > (-10 to: 10) atRandom > > Since > > 10 atRandom > > In fact generates a Natural number and not an Integerâ¦ :-) Indeed > > Julien > > --- > Julien Delplanque > Doctorant Ã lâUniversitÃ© de Lille 1 > http://juliendelplanque.be/phd.html > Equipe Rmod, Inria > BÃ¢timent B 40, Avenue Halley 59650 Villeneuve d'Ascq > NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40 > >> Le 16 avr. 2018 Ã 12:51, Sven Van Caekenberghe <sven(a)stfx.eu> a Ã©crit : >> >> I think >> >> Float randomFrom: -4.1 to: 2.5 >> >> or >> >> Float randomBetween: -4.1 and: 2.5 >> >> would be the most descriptive and compliant to your signature ;-) >> >> An interval does not necessarily contain Floats. >> Going to the class side of Float makes sense because you create a new instance. >> >>> On 16 Apr 2018, at 11:51, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: >>> >>> Hi Pharoers, >>> >>> some random musings about Random numbers :-) >>> >>> In the context of the CORMAS project: >>> http://cormas.cirad.fr/indexeng.htm >>> I would like to propose an API for manipulating random numbers >>> to users who are not developers but modelers of complex systems. >>> >>> In CORMAS, people need to generate a lot of random numbers for simulation for exemple. For example, you can do: >>> >>> Cormas randomFloatFrom: -4.1 to: 2.5 >>> >>> âAt the moment, there is no Pharo API to generate with a one-liner a random float number between two values for example. >>> >>> You can do this for integers: 10 atRandom to generate an integer between 1 to 10. >>> >>> There is atRandom defined on Interval, so can you say : >>> (2.3 to: 4.5) atRandom >>> but it will not generate a random float numbers between 2.3 and 4.5 >>> >>> but numbers like: 2.3, 3.3 or 4.3. >>> because Interval are considered as a Collection. >>> >>> âAny comments about that ? >>> How we can enhance the situation ?â >>> Any interest to introduce a method to produce random float numbers in an interval in Pharo ? >>> >>> âThank youâ >>> -- >>> Serge Stinckwich >>> UMI UMMISCO 209 (SU/IRD/UY1) >>> "Programs must be written for people to read, and only incidentally for machines to execute." >>> http://www.doesnotunderstand.org/ >> >> >

April 16, 2018

Re: [Pharo-users] In P7 scrpt variable to tmp when in debugger

by Marcus Denker

> On 16 Apr 2018, at 11:18, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > >> On 12 Apr 2018, at 17:18, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: >> >> >> >>> On 12 Apr 2018, at 17:06, Hilaire <hilaire(a)drgeo.eu <mailto:hilaire@drgeo.eu>> wrote: >>> >>> Hi Marcus, Benoit, >>> >>> Nice to know. I was testing in a set up with both .changes and source files. So I was suspecting something like what your described. I can imagine in production code your feature to speed up compilation will be appreciated. For Dr. Geo and Smalltalk sketch, it is better to have variable names. >>> >> >> I should have a fix ready tomorrow. >> > > I will for now revert the change: > > https://github.com/pharo-project/pharo/pull/1199 <https://github.com/pharo-project/pharo/pull/1199> > > This way it behaves as people expect, I have an idea how to provide an option for the faster way. > This will come next. 1) added compiler option to compile with source embedded: https://github.com/pharo-project/pharo/pull/1200 <https://github.com/pharo-project/pharo/pull/1200> 2) then we can use this when evaluating, which avoids the double recompile that we did: https://github.com/pharo-project/pharo/pull/1201 <https://github.com/pharo-project/pharo/pull/1201> We regain now a lot of speed by avoiding the double recompile, which had been the real source of the speed problem. The pretty-print of course is still done and costsâ¦ so this could be restructured further. e.g. we could add an explicit option to not pretty print. Marcus

April 16, 2018

Re: [Pharo-users] Some random musings

by jtuchel＠objektfabrik.de

Sven, Serge, Especially in the case of Floats, I think between:and: is *not* a good name. As always, the question is if between:and: is exclusive or inclusive of the border values... So I think the better name is from:to:. I think this name indicates it includes the border values. Joachim Am 16.04.18 um 12:51 schrieb Sven Van Caekenberghe: > I think > > Float randomFrom: -4.1 to: 2.5 > > or > > Float randomBetween: -4.1 and: 2.5 > > would be the most descriptive and compliant to your signature ;-) > > An interval does not necessarily contain Floats. > Going to the class side of Float makes sense because you create a new instance. > >> On 16 Apr 2018, at 11:51, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: >> >> Hi Pharoers, >> >> some random musings about Random numbers :-) >> >> In the context of the CORMAS project: >> http://cormas.cirad.fr/indexeng.htm >> I would like to propose an API for manipulating random numbers >> to users who are not developers but modelers of complex systems. >> >> In CORMAS, people need to generate a lot of random numbers for simulation for exemple. For example, you can do: >> >> Cormas randomFloatFrom: -4.1 to: 2.5 >> >> âAt the moment, there is no Pharo API to generate with a one-liner a random float number between two values for example. >> >> You can do this for integers: 10 atRandom to generate an integer between 1 to 10. >> >> There is atRandom defined on Interval, so can you say : >> (2.3 to: 4.5) atRandom >> but it will not generate a random float numbers between 2.3 and 4.5 >> >> but numbers like: 2.3, 3.3 or 4.3. >> because Interval are considered as a Collection. >> >> âAny comments about that ? >> How we can enhance the situation ?â >> Any interest to introduce a method to produce random float numbers in an interval in Pharo ? >> >> âThank youâ >> -- >> Serge Stinckwich >> UMI UMMISCO 209 (SU/IRD/UY1) >> "Programs must be written for people to read, and only incidentally for machines to execute." >> http://www.doesnotunderstand.org/ > > -- ----------------------------------------------------------------------- Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de Fliederweg 1Â Â Â Â Â Â Â Â Â Â Â Â Â http://www.objektfabrik.de D-71640 Ludwigsburg http://joachimtuchel.wordpress.com Telefon: +49 7141 56 10 86 0Â Â Â Â Â Fax: +49 7141 56 10 86 1

April 16, 2018