February 2018 - Pharo-users

Re: [Pharo-users] UpdatedPharoByExample

by Sean P. DeNigris

John Pfersich wrote > I found a couple of errors in SharingCode.pillar. It would be helpful to include the full URL to the file on GH, although in this case it was unique enough to be google-able. John Pfersich wrote > I couldn't upload a branch. Sorry, I'm a a very infrequent github user, > and I just don't get > it. I feel your pain! But for text files, you can edit directly in the GH UI and there is a button to [create a branch and submit a PR] in one click. John Pfersich wrote > Anyways, lines 359 and 360 probably should be changed to this: Fixed. Thanks! ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Feb. 26, 2018

Re: [Pharo-users] adding 1 year to the date - bug?

by jtuchel＠objektfabrik.de

Am 26.02.18 um 11:13 schrieb Petr Fischer: > So "date addMonths: 12" behaves better for my needs. Thanks Hmm. We've had this discussion just the other day at Lunch. What is a month? Should addMonths: 1 and then subtractMonths: 1 on January 31st bring you back to January 31st? How would you implement that? I guess this is a problem that cannot be solved by a machine without additional context. Does 1 month later mean "on this day next month" or does it mean "exactly as many days in the future as the current month has days"? None of the two? Can one month later be in March when today is January 30th? It seems years and months are a bit incompatible with informatics ;-) In my opinion, there is more info needed than "x months/years later" in order to calculate the correct result. Joachim > > >> Hello, just simple test: >> >> (Date year: 2019 month: 2 day: 26) + 1 year. >> returns: 26 February 2020 >> OK >> >> (Date year: 2020 month: 2 day: 26) + 1 year. >> returns: 25 February 2021 >> What? >> >> (maybe I do not understand something about dates again) >> >> Thanks! pf >> > -- ----------------------------------------------------------------------- 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

Feb. 26, 2018

Re: [Pharo-users] adding 1 year to the date - bug?

by Petr Fischer

So "date addMonths: 12" behaves better for my needs. Thanks > Hello, just simple test: > > (Date year: 2019 month: 2 day: 26) + 1 year. > returns: 26 February 2020 > OK > > (Date year: 2020 month: 2 day: 26) + 1 year. > returns: 25 February 2021 > What? > > (maybe I do not understand something about dates again) > > Thanks! pf >

Feb. 26, 2018

Re: [Pharo-users] adding 1 year to the date - bug?

by Tudor Girba

+1 Doru > On Feb 26, 2018, at 10:54 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > > Forgot to say that this is something you can experience quite often. To me the problem is that 1 year gives a duration immediately. It should work as all units that 1 year is a unit of magnitude 1 and unit year. If you apply this to a date you could make it properly to give the date one year later. > I noticed that problem when I started to use the Units package of Marcus. It works for all units except durations because these are already taken. So for me there would be two benefits changing that. > > Norbert > > >> Am 26.02.2018 um 10:48 schrieb Norbert Hartl <norbert(a)hartl.name>: >> >> >> >>> Am 26.02.2018 um 10:43 schrieb Petr Fischer <petr.fischer(a)me.com>: >>> >>> Hello, just simple test: >>> >>> (Date year: 2019 month: 2 day: 26) + 1 year. >>> returns: 26 February 2020 >>> OK >>> >>> (Date year: 2020 month: 2 day: 26) + 1 year. >>> returns: 25 February 2021 >>> What? >>> >>> (maybe I do not understand something about dates again) >> >> That is a conceptual problem. 1 year is a duration. As it does not know which year it is the normal 365 days. And 2020 is a leap year so has 366 days. Thatâs why the date is shifted. >> >> Norbert > -- www.tudorgirba.com www.feenk.com "What we can governs what we wish."

Feb. 26, 2018

Re: [Pharo-users] how to load compiled code in the image and to change methods already on the stack?

by Steven Costiou

Hi Pablo, thanks :) I will try Hermes. Basic scenario is adding/removing metalinks to a lot of a methods in an iot app: 1- If the add/remove occurs a lot of time, then there is a slowdown due to recompilation of methods. As this is a remote app, i want to try recompiling all methods locally then upload them. I will also try with Hermes. 2- If metalinks are put inside a loop that is running, for now i understand i cannot update the method unless i replace it on the stack. Experimenting that is somewhere in my todolist, but i'm taking any advice ;) Maybe that is not really possible. Steven. Le 2018-02-26 10:36, tesonep(a)gmail.com a Ã©crit : > Hi Steven, > > 1. You can use Hermes through a socket or a file. The only pre-requisite is that both images run similar compatible compilers (usually you can use it from and to Pharo 6.1 and 7) > 2. You can change the method, but if there is an activation context in the stack everything can be wrong. If you change a method you should update the program counter of the stack, and also any other thing can change (for example, temporaries or literals). > Can you describe more the scenario where you want to change the method? > > Cheers, > > On Sat, Feb 24, 2018 at 11:23 AM, Steven Costiou <steven.costiou(a)kloum.io> wrote: > >> Hi, >> >> is this possible somehow to: >> >> - load compiled code in the image? like loading a compiled method instead of loading source then compiling it? >> >> - dynamically change a method that is on the stack? >> >> If so, how? :) >> >> Steven. > > -- > Pablo Tesone. > tesonep(a)gmail.com

Feb. 26, 2018

Re: [Pharo-users] adding 1 year to the date - bug?

by Norbert Hartl

Forgot to say that this is something you can experience quite often. To me the problem is that 1 year gives a duration immediately. It should work as all units that 1 year is a unit of magnitude 1 and unit year. If you apply this to a date you could make it properly to give the date one year later. I noticed that problem when I started to use the Units package of Marcus. It works for all units except durations because these are already taken. So for me there would be two benefits changing that. Norbert > Am 26.02.2018 um 10:48 schrieb Norbert Hartl <norbert(a)hartl.name>: > > > >> Am 26.02.2018 um 10:43 schrieb Petr Fischer <petr.fischer(a)me.com>: >> >> Hello, just simple test: >> >> (Date year: 2019 month: 2 day: 26) + 1 year. >> returns: 26 February 2020 >> OK >> >> (Date year: 2020 month: 2 day: 26) + 1 year. >> returns: 25 February 2021 >> What? >> >> (maybe I do not understand something about dates again) > > That is a conceptual problem. 1 year is a duration. As it does not know which year it is the normal 365 days. And 2020 is a leap year so has 366 days. Thatâs why the date is shifted. > > Norbert

Feb. 26, 2018

Re: [Pharo-users] adding 1 year to the date - bug?

by Norbert Hartl

> Am 26.02.2018 um 10:43 schrieb Petr Fischer <petr.fischer(a)me.com>: > > Hello, just simple test: > > (Date year: 2019 month: 2 day: 26) + 1 year. > returns: 26 February 2020 > OK > > (Date year: 2020 month: 2 day: 26) + 1 year. > returns: 25 February 2021 > What? > > (maybe I do not understand something about dates again) That is a conceptual problem. 1 year is a duration. As it does not know which year it is the normal 365 days. And 2020 is a leap year so has 366 days. Thatâs why the date is shifted. Norbert

Feb. 26, 2018

Re: [Pharo-users] adding 1 year to the date - bug?

by Pavel Krivanek

In Pharo 1 year is a duration of 365 days so it does not reflect leap years. -- Pavel 2018-02-26 10:43 GMT+01:00 Petr Fischer <petr.fischer(a)me.com>: > Hello, just simple test: > > (Date year: 2019 month: 2 day: 26) + 1 year. > returns: 26 February 2020 > OK > > (Date year: 2020 month: 2 day: 26) + 1 year. > returns: 25 February 2021 > What? > > (maybe I do not understand something about dates again) > > Thanks! pf >

Feb. 26, 2018

adding 1 year to the date - bug?

by Petr Fischer

Hello, just simple test: (Date year: 2019 month: 2 day: 26) + 1 year. returns: 26 February 2020 OK (Date year: 2020 month: 2 day: 26) + 1 year. returns: 25 February 2021 What? (maybe I do not understand something about dates again) Thanks! pf

Feb. 26, 2018

Re: [Pharo-users] how to load compiled code in the image and to change methods already on the stack?

by tesonep＠gmail.com

Hi Steven, 1. You can use Hermes through a socket or a file. The only pre-requisite is that both images run similar compatible compilers (usually you can use it from and to Pharo 6.1 and 7) 2. You can change the method, but if there is an activation context in the stack everything can be wrong. If you change a method you should update the program counter of the stack, and also any other thing can change (for example, temporaries or literals). Can you describe more the scenario where you want to change the method? Cheers, On Sat, Feb 24, 2018 at 11:23 AM, Steven Costiou <steven.costiou(a)kloum.io> wrote: > Hi, > > is this possible somehow to: > > - load compiled code in the image? like loading a compiled method instead > of loading source then compiling it? > > - dynamically change a method that is on the stack? > > > > If so, how? :) > > Steven. > -- Pablo Tesone. tesonep(a)gmail.com

Feb. 26, 2018