- Pharo-users - lists.pharo.org

Re: [Pharo-users] Your vm is too oldâ¦.

by StÃ©phane Ducasse

On Jul 25, 2013, at 9:08 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > This was a problem that we also had (when working in Moose), and Esteban fixed it (first the workaround in the image, and then in the VM). We are using this VM since some months now and the problem did not resurface. > > That is why I know it is fixed in the latest stable PharoVM. Ok what igor is probably meaning is that we would prefer to get the system running without having to have a workaround at the image level. > > Cheers, > Doru > > > On Thu, Jul 25, 2013 at 9:03 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > Doru, > > I'm sorry but I was mistaken somehow. I tried always to use the newest VM. I just downloaded a new vm a few minutes ago and now I cannot reproduce the problem anymore. That doesn't mean it won't appear anymore but I'll work with the pharo vm and see if it comes back. > > thanks, > > Norbert > > Am 24.07.2013 um 22:46 schrieb Tudor Girba <tudor(a)tudorgirba.com>: > > > Use the latest stable VM. It should solve the problem. > > > > Doru > > > > > > On Jul 24, 2013, at 10:34 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > > > >> > >> > >> Am 24.07.2013 um 18:21 schrieb StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > >> > >>> > >>> On Jul 24, 2013, at 5:13 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > >>> > >>>> As I cannot work with the pharo VM right now > >>> > >>> what is the problem? > >> > >> I get the DNU SmallInteger>>add: all the time especially when using metacello (Using Versionner I get it nearly every attempt to validate the configuration). This occurred already a few times on the list. > >> > >> > >>> > >>>> I'm back to use Eliots Cog. But If I open a more recent image it complains about my vm being to old. What does it really check in order to complain? Some just version string/number parsing? Is it always sever? > >>>> > >>>> Norbert > >>> > >>> > >> > > > > -- > > www.tudorgirba.com > > > > "Quality cannot be an afterthought." > > > > > > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

July 25, 2013

Re: [Pharo-users] Your vm is too oldâ¦.

by Tudor Girba

This was a problem that we also had (when working in Moose), and Esteban fixed it (first the workaround in the image, and then in the VM). We are using this VM since some months now and the problem did not resurface. That is why I know it is fixed in the latest stable PharoVM. Cheers, Doru On Thu, Jul 25, 2013 at 9:03 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > Doru, > > I'm sorry but I was mistaken somehow. I tried always to use the newest VM. > I just downloaded a new vm a few minutes ago and now I cannot reproduce the > problem anymore. That doesn't mean it won't appear anymore but I'll work > with the pharo vm and see if it comes back. > > thanks, > > Norbert > > Am 24.07.2013 um 22:46 schrieb Tudor Girba <tudor(a)tudorgirba.com>: > > > Use the latest stable VM. It should solve the problem. > > > > Doru > > > > > > On Jul 24, 2013, at 10:34 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > > > >> > >> > >> Am 24.07.2013 um 18:21 schrieb StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr>: > >> > >>> > >>> On Jul 24, 2013, at 5:13 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > >>> > >>>> As I cannot work with the pharo VM right now > >>> > >>> what is the problem? > >> > >> I get the DNU SmallInteger>>add: all the time especially when using > metacello (Using Versionner I get it nearly every attempt to validate the > configuration). This occurred already a few times on the list. > >> > >> > >>> > >>>> I'm back to use Eliots Cog. But If I open a more recent image it > complains about my vm being to old. What does it really check in order to > complain? Some just version string/number parsing? Is it always sever? > >>>> > >>>> Norbert > >>> > >>> > >> > > > > -- > > www.tudorgirba.com > > > > "Quality cannot be an afterthought." > > > > > > > -- www.tudorgirba.com "Every thing has its own flow"

July 25, 2013

Re: [Pharo-users] Your vm is too oldâ¦.

by Norbert Hartl

Doru, I'm sorry but I was mistaken somehow. I tried always to use the newest VM. I just downloaded a new vm a few minutes ago and now I cannot reproduce the problem anymore. That doesn't mean it won't appear anymore but I'll work with the pharo vm and see if it comes back. thanks, Norbert Am 24.07.2013 um 22:46 schrieb Tudor Girba <tudor(a)tudorgirba.com>: > Use the latest stable VM. It should solve the problem. > > Doru > > > On Jul 24, 2013, at 10:34 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > >> >> >> Am 24.07.2013 um 18:21 schrieb StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> >>> >>> On Jul 24, 2013, at 5:13 PM, Norbert Hartl <norbert(a)hartl.name> wrote: >>> >>>> As I cannot work with the pharo VM right now >>> >>> what is the problem? >> >> I get the DNU SmallInteger>>add: all the time especially when using metacello (Using Versionner I get it nearly every attempt to validate the configuration). This occurred already a few times on the list. >> >> >>> >>>> I'm back to use Eliots Cog. But If I open a more recent image it complains about my vm being to old. What does it really check in order to complain? Some just version string/number parsing? Is it always sever? >>>> >>>> Norbert >>> >>> >> > > -- > www.tudorgirba.com > > "Quality cannot be an afterthought." > >

July 25, 2013

Re: [Pharo-users] Your vm is too oldâ¦.

by Norbert Hartl

Doru, that's exactly what I did before. Norbert Am 24.07.2013 um 22:46 schrieb Tudor Girba <tudor(a)tudorgirba.com>: > Use the latest stable VM. It should solve the problem. > > Doru > > > On Jul 24, 2013, at 10:34 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > >> >> >> Am 24.07.2013 um 18:21 schrieb StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> >>> >>> On Jul 24, 2013, at 5:13 PM, Norbert Hartl <norbert(a)hartl.name> wrote: >>> >>>> As I cannot work with the pharo VM right now >>> >>> what is the problem? >> >> I get the DNU SmallInteger>>add: all the time especially when using metacello (Using Versionner I get it nearly every attempt to validate the configuration). This occurred already a few times on the list. >> >> >>> >>>> I'm back to use Eliots Cog. But If I open a more recent image it complains about my vm being to old. What does it really check in order to complain? Some just version string/number parsing? Is it always sever? >>>> >>>> Norbert >>> >>> >> > > -- > www.tudorgirba.com > > "Quality cannot be an afterthought." > >

July 25, 2013

Re: [Pharo-users] Your vm is too oldâ¦.

by Igor Stasenko

On 24 July 2013 22:46, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Use the latest stable VM. It should solve the problem. > Nope. Problem will be solved if we will know exactly what causing it, write test with can reproduce it with 100% guarantee. Using latest VM is not recipe from disease. Unfortunately, we still don't have reproducible case and that blocks us from fixing it. > Doru > -- Best regards, Igor Stasenko.

July 24, 2013

Re: [Pharo-users] Your vm is too oldâ¦.

by Tudor Girba

Use the latest stable VM. It should solve the problem. Doru On Jul 24, 2013, at 10:34 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > > > Am 24.07.2013 um 18:21 schrieb StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > >> >> On Jul 24, 2013, at 5:13 PM, Norbert Hartl <norbert(a)hartl.name> wrote: >> >>> As I cannot work with the pharo VM right now >> >> what is the problem? > > I get the DNU SmallInteger>>add: all the time especially when using metacello (Using Versionner I get it nearly every attempt to validate the configuration). This occurred already a few times on the list. > > >> >>> I'm back to use Eliots Cog. But If I open a more recent image it complains about my vm being to old. What does it really check in order to complain? Some just version string/number parsing? Is it always sever? >>> >>> Norbert >> >> > -- www.tudorgirba.com "Quality cannot be an afterthought."

July 24, 2013

Re: [Pharo-users] Your vm is too oldâ¦.

by Norbert Hartl

Am 24.07.2013 um 18:21 schrieb StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > > On Jul 24, 2013, at 5:13 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > >> As I cannot work with the pharo VM right now > > what is the problem? I get the DNU SmallInteger>>add: all the time especially when using metacello (Using Versionner I get it nearly every attempt to validate the configuration). This occurred already a few times on the list. > >> I'm back to use Eliots Cog. But If I open a more recent image it complains about my vm being to old. What does it really check in order to complain? Some just version string/number parsing? Is it always sever? >> >> Norbert > >

July 24, 2013

Re: [Pharo-users] Bug in Date>>readFrom:pattern: ? Pharo2.0

by Sven Van Caekenberghe

On 24 Jul 2013, at 18:20, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > I remember that once camillo suggested to use the same approach as in dart where you can specify a strategy. The ZTimestamp package contains such an example-based parser/formatter (load from the config browser or from http://www.smalltalkhub.com/#!/~SvenVanCaekenberghe/Neo) that can do what you want and much more, like multi-language weeks/months, for formatting & parsing. ((ZTimestampFormat fromString: '3.2.01') createDate; parse: '4.2.13') = (Date newDay: 4 month: 2 year: 2013 ) It is based on how things are done in Go. Read the class docs & tests for more information. You could subclass ZTimestampFormat and override #parseYearTwoDigitsFrom: to fine-tune the behaviour of 2 digit year specifications. Sven >> I agree >> >> The comment of yyyymmdd is saying >> "Format the date in ISO 8601 standard like '2002-10-22' >> The result is of fixed size 10 characters long.." >> >> so I would say the selector is not choosen very careful. >> >> There is a discussion in Fogbuz about >>readFrom:pattern: >> https://pharo.fogbugz.com/default.asp?11222 >> >> Sabine >> >> On Wed, Jul 24, 2013 at 2:56 PM, Mariano Martinez Peck [via Smalltalk] >> <[hidden email]> wrote: >> >> > I also hate #yyyymmdd >> > >> > Date today yyyymmdd -> '2013-07-24' >> > >> > I would expect '20130724' >> > >> > Cheers, >> > >> > >> > On Wed, Jul 24, 2013 at 5:59 AM, Sabine KnÃ¶fel <[hidden email]> wrote: >> >> >> >> Hi, >> >> >> >> I created a bug, hoping that I filled out every field correctly. >> >> >> >> >> >> https://pharo.fogbugz.com/f/cases/11222/Date-readFrom-pattern-year-2-decima… >> >> >> >> Sabine >> >> >> >> On Wed, Jul 24, 2013 at 9:52 AM, StÃ©phane Ducasse [via Smalltalk] >> >> <[hidden email]> wrote: >> >> >> >> > Hello Sabine >> >> > probably a bug. >> >> > If you can write some tests and publish them on the bugtracker this will >> >> > help. >> >> > If you provide the fix (it will be faster to get it fixed) please run >> >> > the >> >> > tests to make sure that we do not >> >> > introduce side effects. >> >> > >> >> > Stef >> >> > >> >> >> Hi, >> >> >> >> >> >> Date readFrom: '4.2.13' readStream pattern: 'd.m.yy' >> >> >> >> >> >> Does not return 4.2.2013 but 4.2.0013 >> >> >> >> >> >> The comment is saying >> >> >> "A year given using only two decimals is considered to be >2000" >> >> >> >> >> >> So, the comment is not ok or this is a bug? >> >> >> >> >> >> Sabine >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> View this message in context: >> >> >> >> >> >> http://forum.world.st/Bug-in-Date-readFrom-pattern-Pharo2-0-tp4700427.html >> >> >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> >> >> >> >> > >> >> > >> >> > >> >> > >> >> > ________________________________ >> >> > If you reply to this email, your message will be added to the discussion >> >> > below: >> >> > >> >> > http://forum.world.st/Bug-in-Date-readFrom-pattern-Pharo2-0-tp4700427p47004… >> >> > To unsubscribe from Bug in Date>>readFrom:pattern: ? Pharo2.0, click >> >> > here. >> >> > NAML >> >> >> >> ________________________________ >> >> View this message in context: Re: Bug in Date>>readFrom:pattern: ? >> >> Pharo2.0 >> >> >> >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> > >> > >> > >> > >> > -- >> > Mariano >> > http://marianopeck.wordpress.com >> > >> > >> > ________________________________ >> > If you reply to this email, your message will be added to the discussion >> > below: >> > http://forum.world.st/Bug-in-Date-readFrom-pattern-Pharo2-0-tp4700427p47005… >> > To unsubscribe from Bug in Date>>readFrom:pattern: ? Pharo2.0, click here. >> > NAML >> >> View this message in context: Re: Bug in Date>>readFrom:pattern: ? Pharo2.0 >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

July 24, 2013

Re: [Pharo-users] [Moose-dev] Re: [ann] snapshotcello

by Dale K. Henrichs

----- Original Message ----- | From: "Tudor Girba" <tudor(a)tudorgirba.com> | To: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org> | Cc: "Moose-related development" <moose-dev(a)iam.unibe.ch>, "Pharo Development List" <pharo-dev(a)lists.pharo.org> | Sent: Wednesday, July 24, 2013 12:07:48 AM | Subject: Re: [Pharo-users] [Moose-dev] Re: [ann] snapshotcello | | Hi, | | On Jul 23, 2013, at 11:51 PM, "Dale K. Henrichs" | <dale.henrichs(a)gemtalksystems.com> wrote: | | > Stef, | > | > I haven't completely wrapped my brain around what SnapshotCello | > does so I don't have an informed opinion ... the fact that you | > found a need to invent SnapshotCello does speak volumes to the | > fact that there is a need that is going unmet:). | | What is not clear? I would be interested in describing our scenario | in more details because I think this is a development pattern. But, | I need some concrete questions to start from. I do not completely understand what SnapshotCello is actually doing let alone why it is doing what it is doing ... So I need to spend time with it to "wrap my brain around it" then I can ask concrete questions.... | | > However, I don't like the fact that you end up sending a non-spec | > message to make this work (#populateSpec:with:). Tools like | > Versioner will not be able to rewrite a method like this correctly | > so it is a less than satisfactory workaround to the method literal | > limit. | | I still do not understand why Versionner would be affected by the | current versions given that we are only generating versions that | should be immutable hence no need for management. I made my comments without having wrapped my head around SnapshotCello and it is my standard reaction to non-spec-based message sends ... I reserve the right to someday switch to a non-class-based implementation for Metacello and problems like too many literals in a method will no longer be a problem (and the tool many literals issue is but one of the forces driving me away from class-based specs), but specs that are generated dynamically based on data gleaned from arbitrary message sends will not be mappable. So I continue to repeat the message that Metacello does not support the dynamic generation of specs. In your particular case you are probably living within acceptable bounds, but the very existence of "message sends within a spec" may encourage other folks to try their hand at dynamic generation....and we are off to the races:) So I continue to repeat the message that Metacello does not support the dynamic generation of specs. | | > With that said it _is_ performing a useful function ... | > | > I have recently come up with an approach to addressing the method | > literal limit from a slightly different angle and I would assume | > that SnapshotCello could be recast to use this "approved approach" | > when the new techinique becomes available. At that time it would | > make sense to roll the SnapshotCello funtionality into the | > MetacelloToolBox... | | Having a different way to store the information should be no problem. | I am curious about your ideas. I've tossed out some of my ideas in a post in the metacello mailing list[1]. And that would be a good place to discusss this further... Dale [1] http://forum.world.st/Loading-problem-in-Seaside-tc4699965.html

July 24, 2013

Re: [Pharo-users] [Pharo-dev] [Moose-dev] Re: [ann] snapshotcello

by Tudor Girba

Hi, I would be happy to blend Snapshotcello into Metacello. Cheers, Doru On Jul 24, 2013, at 9:05 PM, "Dale K. Henrichs" <dale.henrichs(a)gemtalksystems.com> wrote: > > > ----- Original Message ----- > | From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> > | To: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > | Cc: "Moose-related development" <moose-dev(a)iam.unibe.ch>, "Any question about pharo is welcome" > | <pharo-users(a)lists.pharo.org> > | Sent: Tuesday, July 23, 2013 11:48:27 PM > | Subject: Re: [Pharo-dev] [Moose-dev] Re: [ann] snapshotcello > | > | > | On Jul 23, 2013, at 11:51 PM, Dale K. Henrichs > | <dale.henrichs(a)gemtalksystems.com> wrote: > | > | > Stef, > | > > | > I haven't completely wrapped my brain around what SnapshotCello > | > does so I don't have an informed opinion ... the fact that you > | > found a need to invent SnapshotCello does speak volumes to the > | > fact that there is a need that is going unmet:). > | > > | > However, I don't like the fact that you end up sending a non-spec > | > message to make this work (#populateSpec:with:). Tools like > | > Versioner will not be able to rewrite a method like this correctly > | > so it is a less than satisfactory workaround to the method literal > | > limit. > | > | Indeed. May be in the future we could recreate a simple compliant > | spec driven method by interpreting the > | existing configuration trees but this requires some work. > > Absolutely and it would be work that I'd be willing to do ... From that perspective SnapshotCello is a very good spec for what you and the Moose team need. > > Dale > -- www.tudorgirba.com "Every thing has its own flow."

July 24, 2013