Re: [Pharo-users] ui slowness on newly installed ubuntu 13.04 64bit

[Stéphane Ducasse]

could we get the image so that we can try?

Stef

On Jun 7, 2013, at 8:27 AM, Marcus Denker  wrote:

> 
> On Jun 6, 2013, at 5:12 PM, Paul DeBruicker  wrote:
> 
>> Hi Damien,
>> 
>> 
>>  Because of the attached Message Tally outputs I don't think the problem
>> is specific to changes I've made to an image.  I also don't think that
>> there is much differnece between Eliots vm or the pharo ppa vm.  The
>> Message Tally outputs are from profiling the UI while finding the
>> senders of #setUp using various VM & image combinations.On squeak
>> finding the senders of #setUp seems instantaneous.On Pharo it takes
>> multiple seconds to find and display the senders.
>> 
> 
> This is really strange… here even doing "senders of" for all the >6000 senders
> of ifTrue: is quite fast for 2.0 and even faster in 3.0.
> 
> So I really wonder what the problem is...
> 
>   Marcus

[Pharo-users] Changes-File & caching

[Markus Fritsche]

Hello,

I reported a bug I found in
https://pharo.fogbugz.com/default.asp?10849_d0g95e46s78671vi

The issue was closed in fogbugz. I couldn't really figure out why, until I
looked at Penelope to find out that bug was considered a duplicate.

I had a hard time finding that information and the information on the
duplicate (I could figure it out yesterday night, but can't reproduce the
way to find the information today). From what I understood yesterday, this
bug is supposed to be fixed in Pharo-3.0?

The images that are offered for downloading seem to all include this bug. I
have a notebook with ubuntu-13.04 and 8GB RAM, of which around 7GB are used
for hard disk caching. As far as I understood from reading the bug tracking
entries, heavy caching triggers the bug earlier?

Anyhow, with this bug, the changes file gets garbaged (or, at least, the
pointers to it) and the image is unuseable. Abandoning the RemoteString
error message looks to the user as if the issue wasn't all that bad, but is
a nuclear attack on the image soon to come.

Correct me if I am wrong please.

About issue tracking: is the process closed to the public on purpose? I have
to admit I misused the google code bugtracker in the past, because I
reported an incident from the user point of view and later learned, that the
bug reporting & fixing process was meant to be used only from a developers
perspective.

When I have a "user" issue - am I supposed to report to the mailing list
instead and an issue will be created by the pharo core team?

Kind regards,
  Markus

Re: [Pharo-users] ui slowness on newly installed ubuntu 13.04 64bit

[Camillo Bruni]

On 2013-06-07, at 08:27, Marcus Denker  wrote:

> 
> On Jun 6, 2013, at 5:12 PM, Paul DeBruicker  wrote:
> 
>> Hi Damien,
>> 
>> 
>>  Because of the attached Message Tally outputs I don't think the problem
>> is specific to changes I've made to an image.  I also don't think that
>> there is much differnece between Eliots vm or the pharo ppa vm.  The
>> Message Tally outputs are from profiling the UI while finding the
>> senders of #setUp using various VM & image combinations.On squeak
>> finding the senders of #setUp seems instantaneous.On Pharo it takes
>> multiple seconds to find and display the senders.
>> 
> 
> This is really strange… here even doing "senders of" for all the >6000 senders
> of ifTrue: is quite fast for 2.0 and even faster in 3.0.
> 
> So I really wonder what the problem is...

the provided profiling evidence shows the same. Pharo 1.4 / 2.0 on cog doesn't
show any anomalies :/. But I must say that I had an image as well that behaved 
similarly recently...

Re: [Pharo-users] Changes-File & caching

[Marcus Denker]

On Jun 7, 2013, at 10:26 AM, Markus Fritsche  wrote:

> Hello,
> 
> I reported a bug I found in
> https://pharo.fogbugz.com/default.asp?10849_d0g95e46s78671vi
> 
> The issue was closed in fogbugz. I couldn't really figure out why, until I
> looked at Penelope to find out that bug was considered a duplicate.
> 

Normally I thought that fogbugz should send you updates on bugs you reported?
We need to check that.

> I had a hard time finding that information and the information on the
> duplicate (I could figure it out yesterday night, but can't reproduce the
> way to find the information today). From what I understood yesterday, this
> bug is supposed to be fixed in Pharo-3.0?
> 
In this case, we have fixed in in 3.0 and 2.0 (the bug as a "Parent Case" for 
2.0,
this was decided in the discussion and done).
We often fix things first in 3.0 to test and then fix it in 2.0 so we are sure 
the fix
works.

> The images that are offered for downloading seem to all include this bug.

The problem is that the 2.0 files referenced directly on pharo-project.org are 
pointing
to the last *release*, while the fixes we do in 2.0 are only in the nightly 
builds that you can
find on http://files.pharo.org/image/20/ for example

I already was thinking that this is a problem, we need to discuss what to do.

Maybe we should instead have pharo-project.org point on the latest 2.0?


> 
> Anyhow, with this bug, the changes file gets garbaged (or, at least, the
> pointers to it) and the image is unuseable. Abandoning the RemoteString
> error message looks to the user as if the issue wasn't all that bad, but is
> a nuclear attack on the image soon to come.
> 
So there are two problems:

1) the "RemoteString past end of file" on recent linux.

2) Something strange happens sometimes that reading the source fails.

 
https://pharo.fogbugz.com/f/cases/7559/Plugins-Primitives-no-longer-work-after-a-while
 (it has a parent case for 2.0)


> About issue tracking: is the process closed to the public on purpose?

FugBugz does not allow read access for anonymous users. We *really* don't like 
this
but it can't be changed. That is why we added bugs.pharo.org where you can get 
an
account immediately *and* view all issues

Maybe this is not enough and we need to abandon Fogbugz because it just is "too 
closed"?

> I have
> to admit I misused the google code bugtracker in the past, because I
> reported an incident from the user point of view and later learned, that the
> bug reporting & fixing process was meant to be used only from a developers
> perspective.
> 
Not really…. but it is difficult to do both in the same system. Maybe we need
two bug trackers? One for bugs and one to funnel through improvements and fixes?

> When I have a "user" issue - am I supposed to report to the mailing list
> instead and an issue will be created by the pharo core team?
> 

No, normally the idea is that people should report bug entires.

But one thing that is always a problem is man-power: Not many people look at 
the bug 
tracker. (To me it always feels as if I am the only one…).

This means in turn, we need to sometimes deal with bugs in a way that might not 
be perfect.
The only way to make it better is if more people share the load. I don't see 
any other way.

Marcus

Re: [Pharo-users] Changes-File & caching

[Sven Van Caekenberghe]

Hi Markus,

On 07 Jun 2013, at 10:26, Markus Fritsche  wrote:

> Hello,
> 
> I reported a bug I found in
> https://pharo.fogbugz.com/default.asp?10849_d0g95e46s78671vi
> 
> The issue was closed in fogbugz. I couldn't really figure out why, until I
> looked at Penelope to find out that bug was considered a duplicate.

Yes, I closed the bug because it was a duplicate.

> I had a hard time finding that information and the information on the
> duplicate (I could figure it out yesterday night, but can't reproduce the
> way to find the information today). From what I understood yesterday, this
> bug is supposed to be fixed in Pharo-3.0?
> 
> The images that are offered for downloading seem to all include this bug. I
> have a notebook with ubuntu-13.04 and 8GB RAM, of which around 7GB are used
> for hard disk caching. As far as I understood from reading the bug tracking
> entries, heavy caching triggers the bug earlier?
> 
> Anyhow, with this bug, the changes file gets garbaged (or, at least, the
> pointers to it) and the image is unuseable. Abandoning the RemoteString
> error message looks to the user as if the issue wasn't all that bad, but is
> a nuclear attack on the image soon to come.
> 
> Correct me if I am wrong please.

Yes, it is an important problem (but the trigger is a change in Ubuntu 13.04). 
I am not an Ubuntu desktop user, I can only hope that those who are will help.

> About issue tracking: is the process closed to the public on purpose? I have
> to admit I misused the google code bugtracker in the past, because I
> reported an incident from the user point of view and later learned, that the
> bug reporting & fixing process was meant to be used only from a developers
> perspective.
> 
> When I have a "user" issue - am I supposed to report to the mailing list
> instead and an issue will be created by the pharo core team?
> 
> Kind regards,
>  Markus

Pharo is open source and developed in the open, after the switch to Fogzbug 
things are not yet perfect: it is too hard for casual users. This will improve 
slowly.

Rest assured: you are helping a lot by reporting issues from a user perspective 
!

Thanks, keep pushing !

Sven

Re: [Pharo-users] Changes-File & caching

[Markus Fritsche]

Hello Sven & List,

On 07.06.2013 10:45, Sven Van Caekenberghe wrote:

Yes, it is an important problem (but the trigger is a change in Ubuntu 13.04). 
I am not an Ubuntu desktop user, I can only hope that those who are will help.
Well, I have 13.04 on a few laptops (2GB Atom netbook, 8GB i7 dual core 
and 6GB AMD 4Core) with different file systems (ext4, btrfs) on them, so 
I have quite a few configurations at hand to test with.


The RemoteString-Error during updates has been fixed; as I see the files 
referenced by the download links have been replaced. The only "old" 
image left I found was the one titled "Pharo 2.0 image" on 
http://www.pharo-project.org/pharo-download which raises the error in 
ScriptLoaderupdate>>#20605

Re: [Pharo-users] Changes-File & caching

[Sven Van Caekenberghe]

On 07 Jun 2013, at 11:07, Markus Fritsche  wrote:

> Hello Sven & List,
> 
> On 07.06.2013 10:45, Sven Van Caekenberghe wrote:
>> Yes, it is an important problem (but the trigger is a change in Ubuntu 
>> 13.04). I am not an Ubuntu desktop user, I can only hope that those who are 
>> will help.
> Well, I have 13.04 on a few laptops (2GB Atom netbook, 8GB i7 dual core and 
> 6GB AMD 4Core) with different file systems (ext4, btrfs) on them, so I have 
> quite a few configurations at hand to test with.

Great, we need more Linux Desktop users, the community it too Mac centric ;-)

> The RemoteString-Error during updates has been fixed; as I see the files 
> referenced by the download links have been replaced. The only "old" image 
> left I found was the one titled "Pharo 2.0 image" on 
> http://www.pharo-project.org/pharo-download which raises the error in 
> ScriptLoaderupdate>>#20605

We need to fix that then.

Thanks for the feedback.

Sven

--
Sven Van Caekenberghe
Proudly supporting Pharo
http://pharo.org
http://association.pharo.org
http://consortium.pharo.org

Re: [Pharo-users] Changes-File & caching

[Markus Fritsche]

Hello Marcus & List,

On 07.06.2013 10:44, Marcus Denker wrote:
Normally I thought that fogbugz should send you updates on bugs you 
reported? We need to check that. 

I got one mail with an URL that I could check for updates...

In this case, we have fixed in in 3.0 and 2.0 (the bug as a "Parent Case" for 
2.0,
this was decided in the discussion and done).
We often fix things first in 3.0 to test and then fix it in 2.0 so we are sure 
the fix
works.

Thank you for explaining. I admit it was late yesterday ;-)

So there are two problems:

1) the "RemoteString past end of file" on recent linux.

2) Something strange happens sometimes that reading the source fails.

  
https://pharo.fogbugz.com/f/cases/7559/Plugins-Primitives-no-longer-work-after-a-while
  (it has a parent case for 2.0)
Can you link to Penelope about the second issue? I'd like to help hunt 
these two since ubuntu-13.04 is my primary system on a few machines, big 
to small.

FugBugz does not allow read access for anonymous users. We *really* don't like 
this
but it can't be changed. That is why we added bugs.pharo.org where you can get 
an
account immediately *and* view all issues

Penelope only lists active bugs?
As far as I see, it doesn't have a full text search - that would 
probably make things more simple.

No, normally the idea is that people should report bug entires.

Ok, thanks for clarification. I wasn't sure after poking around a bit.

Kind regards, Markus

Re: [Pharo-users] Changes-File & caching

[Marcus Denker]

On Jun 7, 2013, at 11:20 AM, Markus Fritsche  wrote:

>>  
>> https://pharo.fogbugz.com/f/cases/7559/Plugins-Primitives-no-longer-work-after-a-while
>>  (it has a parent case for 2.0)
> Can you link to Penelope about the second issue? I'd like to help hunt these 
> two since ubuntu-13.04 is my primary system on a few machines, big to small.

Sadly not because of

10157 http://bugs.pharo.org is not in sync with FogBugz

https://pharo.fogbugz.com/f/cases/10157/http-bugs-pharo-org-is-not-in-sync-with-FogBugz


>> FugBugz does not allow read access for anonymous users. We *really* don't 
>> like this
>> but it can't be changed. That is why we added bugs.pharo.org where you can 
>> get an
>> account immediately *and* view all issues
> Penelope only lists active bugs?

Normally that is the idea, yes.

> As far as I see, it doesn't have a full text search - that would probably 
> make things more simple.

Yes, the problem is that man power is limited and even though we really really 
want all these things,
the sad reality is that they are only done when they are done. I have not found 
any other solution than
to do, one tiny trivial step at a time...

Marcus

Re: [Pharo-users] Changes-File & caching

[Camillo Bruni]

On 2013-06-07, at 11:20, Markus Fritsche  wrote:

> Hello Marcus & List,
> 
> On 07.06.2013 10:44, Marcus Denker wrote:
>> Normally I thought that fogbugz should send you updates on bugs you 
>> reported? We need to check that. 
> I got one mail with an URL that I could check for updates...
>> In this case, we have fixed in in 3.0 and 2.0 (the bug as a "Parent Case" 
>> for 2.0,
>> this was decided in the discussion and done).
>> We often fix things first in 3.0 to test and then fix it in 2.0 so we are 
>> sure the fix
>> works.
> Thank you for explaining. I admit it was late yesterday ;-)
>> So there are two problems:
>> 
>> 1) the "RemoteString past end of file" on recent linux.
>> 
>> 2) Something strange happens sometimes that reading the source fails.
>> 
>>  
>> https://pharo.fogbugz.com/f/cases/7559/Plugins-Primitives-no-longer-work-after-a-while
>>  (it has a parent case for 2.0)
> Can you link to Penelope about the second issue? I'd like to help hunt these 
> two since ubuntu-13.04 is my primary system on a few machines, big to small.

you can register on the penelope page.
avoid the dot in your gmail address (BTW: gmail ignores the dots anyway. you 
can put as many dots as you want and still receive mails).

Re: [Pharo-users] Changes-File & caching

[Marcus Denker]

On Jun 7, 2013, at 11:28 AM, Camillo Bruni  wrote:

> 
> On 2013-06-07, at 11:20, Markus Fritsche  wrote:
> 
>> Hello Marcus & List,
>> 
>> On 07.06.2013 10:44, Marcus Denker wrote:
>>> Normally I thought that fogbugz should send you updates on bugs you 
>>> reported? We need to check that. 
>> I got one mail with an URL that I could check for updates...
>>> In this case, we have fixed in in 3.0 and 2.0 (the bug as a "Parent Case" 
>>> for 2.0,
>>> this was decided in the discussion and done).
>>> We often fix things first in 3.0 to test and then fix it in 2.0 so we are 
>>> sure the fix
>>> works.
>> Thank you for explaining. I admit it was late yesterday ;-)
>>> So there are two problems:
>>> 
>>> 1) the "RemoteString past end of file" on recent linux.
>>> 
>>> 2) Something strange happens sometimes that reading the source fails.
>>> 
>>> 
>>> https://pharo.fogbugz.com/f/cases/7559/Plugins-Primitives-no-longer-work-after-a-while
>>> (it has a parent case for 2.0)
>> Can you link to Penelope about the second issue? I'd like to help hunt these 
>> two since ubuntu-13.04 is my primary system on a few machines, big to small.
> 
> you can register on the penelope page.
> avoid the dot in your gmail address (BTW: gmail ignores the dots anyway. you 
> can put as many dots as you want and still receive mails).

We should add a bug tracker entry for that, too.

Marcus

[Pharo-users] account search

[Camillo Bruni]

who is rem...@me.com  on fogbugz?

Re: [Pharo-users] Changes-File & caching

[Markus Fritsche]

On 07.06.2013 11:27, Camillo Bruni wrote:

you can register on the penelope page.
avoid the dot in your gmail address (BTW: gmail ignores the dots anyway. you 
can put as many dots as you want and still receive mails).

Ah, thanks - I think I used that form before with the dot.

When should I consider myself being a monkey?

Kind regards,
  Markus

Re: [Pharo-users] account search

[Sven Van Caekenberghe]

On 07 Jun 2013, at 11:42, Camillo Bruni  wrote:

> who is rem...@me.com  on fogbugz?

I don't know, but I am pretty sure you can safely remove that account :-)

Re: [Pharo-users] DateAndTime>>asTime

[José Comesaña]

Hello everybody.

I would like to add a new improvement to this thread.

I have noticed that Date class has a bug, or at least something to improve
in readFrom:pattern: method. The initial comment states that "A year given
using only two decimals is considered to be >2000.".

But this seems to be incorrect: if you evaluate

Date readFrom: '07/06/13' readStream pattern: 'd/m/y'

you get:

 7 June 0013 instead of  7 June 2013.

I am working with version #20605

Thank you all for your great work.

Regards.


2013/6/6 Camillo Bruni 

> can you save an image with the inspector opened on both x and y, x asTime
> and y asTime
> and provide a link to it? like that I can inspect it in all detail...
>
> On 2013-06-06, at 17:51, dmacq  wrote:
>
> > I tried it again this morning and still had the problem.
> >
> > This is interesting.
> >
> > | x y |
> > x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7.
> > y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5 second:
> 7.
> > x = y  <-- True
> >
> > But
> > | x y |
> > x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7.
> > y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5 second:
> 7.
> > x asTime = y asTime <- False
> >
> >
> >
> > --
> > View this message in context:
> http://forum.world.st/DateAndTime-asTime-tp4691870p4691988.html
> > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
> >
>
>
>

Re: [Pharo-users] DateAndTime>>asTime

[Sven Van Caekenberghe]

Hi José,

On 07 Jun 2013, at 12:02, José Comesaña  wrote:

> Hello everybody. 
> 
> I would like to add a new improvement to this thread.
> 
> I have noticed that Date class has a bug, or at least something to improve in 
> readFrom:pattern: method. The initial comment states that "A year given using 
> only two decimals is considered to be >2000.". 
> 
> But this seems to be incorrect: if you evaluate 
> 
> Date readFrom: '07/06/13' readStream pattern: 'd/m/y'
> 
> you get:
> 
>  7 June 0013 instead of  7 June 2013.
> 
> I am working with version #20605

The fix would be quite easy:

  year := (inputStream next: 2) asInteger

should be

  year := 2000 + (inputStream next: 2) asInteger

A more important problem is that there are no users of #readFrom:pattern: in 
the system, not even unit tests. If we want to keep the methods, someone should 
start by writing a couple of unit tests.

Sven

> Thank you all for your great work.
> 
> Regards.
> 
> 
> 2013/6/6 Camillo Bruni 
> can you save an image with the inspector opened on both x and y, x asTime and 
> y asTime
> and provide a link to it? like that I can inspect it in all detail...
> 
> On 2013-06-06, at 17:51, dmacq  wrote:
> 
> > I tried it again this morning and still had the problem.
> >
> > This is interesting.
> >
> > | x y |
> > x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7.
> > y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5 second: 7.
> > x = y  <-- True
> >
> > But
> > | x y |
> > x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7.
> > y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5 second: 7.
> > x asTime = y asTime <- False
> >
> >
> >
> > --
> > View this message in context: 
> > http://forum.world.st/DateAndTime-asTime-tp4691870p4691988.html
> > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
> >
> 
> 
> 

Re: [Pharo-users] Changes-File & caching

[Marcus Denker]

On Jun 7, 2013, at 11:47 AM, Markus Fritsche  wrote:

> On 07.06.2013 11:27, Camillo Bruni wrote:
>> you can register on the penelope page.
>> avoid the dot in your gmail address (BTW: gmail ignores the dots anyway. you 
>> can put as many dots as you want and still receive mails).
> Ah, thanks - I think I used that form before with the dot.
> 
> When should I consider myself being a monkey?
> 
When you are a machine… the idea is that is a trivial captcha.  Maybe too 
complex even for humans;-)

Marcus

Re: [Pharo-users] DateAndTime>>asTime

[José Comesaña]

Thank you Sven.

I had made the fixes myself, creating a new class for dates (I don't need
the complexity of Date just for determining if a date is past, I don't need
date arithmetic either). I just wanted to inform, mainly because the bug
seems to be still present in Pharo 3.0.

Anyway, your solution does not work for the 'd/m/y' pattern, although it
does for 'd/m/yy'.

I could write the tests you suggest, if you think they are interesting.

Regards

2013/6/7 Sven Van Caekenberghe 

> Hi José,
>
> On 07 Jun 2013, at 12:02, José Comesaña  wrote:
>
> > Hello everybody.
> >
> > I would like to add a new improvement to this thread.
> >
> > I have noticed that Date class has a bug, or at least something to
> improve in readFrom:pattern: method. The initial comment states that "A
> year given using only two decimals is considered to be >2000.".
> >
> > But this seems to be incorrect: if you evaluate
> >
> > Date readFrom: '07/06/13' readStream pattern: 'd/m/y'
> >
> > you get:
> >
> >  7 June 0013 instead of  7 June 2013.
> >
> > I am working with version #20605
>
> The fix would be quite easy:
>
>   year := (inputStream next: 2) asInteger
>
> should be
>
>   year := 2000 + (inputStream next: 2) asInteger
>
> A more important problem is that there are no users of #readFrom:pattern:
> in the system, not even unit tests. If we want to keep the methods, someone
> should start by writing a couple of unit tests.
>
> Sven
>
> > Thank you all for your great work.
> >
> > Regards.
> >
> >
> > 2013/6/6 Camillo Bruni 
> > can you save an image with the inspector opened on both x and y, x
> asTime and y asTime
> > and provide a link to it? like that I can inspect it in all detail...
> >
> > On 2013-06-06, at 17:51, dmacq  wrote:
> >
> > > I tried it again this morning and still had the problem.
> > >
> > > This is interesting.
> > >
> > > | x y |
> > > x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7.
> > > y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5
> second: 7.
> > > x = y  <-- True
> > >
> > > But
> > > | x y |
> > > x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7.
> > > y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5
> second: 7.
> > > x asTime = y asTime <- False
> > >
> > >
> > >
> > > --
> > > View this message in context:
> http://forum.world.st/DateAndTime-asTime-tp4691870p4691988.html
> > > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
> > >
> >
> >
> >
>
>
>

Re: [Pharo-users] account search

[Clément Bera]

No don't remove it.

It is when someone is assigned to a project and wants to be removed. Then
he selects this guy instead.


2013/6/7 Sven Van Caekenberghe 

>
> On 07 Jun 2013, at 11:42, Camillo Bruni  wrote:
>
> > who is rem...@me.com  on fogbugz?
>
> I don't know, but I am pretty sure you can safely remove that account :-)
>
>
>
>


-- 
Clément Béra
Mate Virtual Machine Engineer
Bâtiment B 40, avenue Halley 59650 *Villeneuve d'Ascq*

Re: [Pharo-users] DateAndTime>>asTime

[Donald]

On 6/6/2013 2:14 PM, Camillo Bruni wrote:

can you save an image with the inspector opened on both x and y, x asTime and y 
asTime
and provide a link to it? like that I can inspect it in all detail...


yes. probably tomorrow.

please ping me if I forget.

thanks


On 2013-06-06, at 17:51, dmacq  wrote:


I tried it again this morning and still had the problem.

This is interesting.

| x y |
x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7.
y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5 second: 7.
x = y  <-- True

But
| x y |
x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7.
y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5 second: 7.
x asTime = y asTime <- False



--
View this message in context: 
http://forum.world.st/DateAndTime-asTime-tp4691870p4691988.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.






--
Donald [|]

A bad day in [] is better than a good day in {}

Re: [Pharo-users] DateAndTime>>asTime

[Sven Van Caekenberghe]

On 07 Jun 2013, at 13:26, José Comesaña  wrote:

> Thank you Sven.
> 
> I had made the fixes myself, creating a new class for dates (I don't need the 
> complexity of Date just for determining if a date is past, I don't need date 
> arithmetic either). I just wanted to inform, mainly because the bug seems to 
> be still present in Pharo 3.0.
> 
> Anyway, your solution does not work for the 'd/m/y' pattern, although it does 
> for 'd/m/yy'.

Depends on what a single y means, right ?

> I could write the tests you suggest, if you think they are interesting. 

Yes, please do: with a good set of tests, we can discuss using concrete 
examples. 

> Regards
> 
> 2013/6/7 Sven Van Caekenberghe 
> Hi José,
> 
> On 07 Jun 2013, at 12:02, José Comesaña  wrote:
> 
> > Hello everybody.
> >
> > I would like to add a new improvement to this thread.
> >
> > I have noticed that Date class has a bug, or at least something to improve 
> > in readFrom:pattern: method. The initial comment states that "A year given 
> > using only two decimals is considered to be >2000.".
> >
> > But this seems to be incorrect: if you evaluate
> >
> > Date readFrom: '07/06/13' readStream pattern: 'd/m/y'
> >
> > you get:
> >
> >  7 June 0013 instead of  7 June 2013.
> >
> > I am working with version #20605
> 
> The fix would be quite easy:
> 
>   year := (inputStream next: 2) asInteger
> 
> should be
> 
>   year := 2000 + (inputStream next: 2) asInteger
> 
> A more important problem is that there are no users of #readFrom:pattern: in 
> the system, not even unit tests. If we want to keep the methods, someone 
> should start by writing a couple of unit tests.
> 
> Sven
> 
> > Thank you all for your great work.
> >
> > Regards.
> >
> >
> > 2013/6/6 Camillo Bruni 
> > can you save an image with the inspector opened on both x and y, x asTime 
> > and y asTime
> > and provide a link to it? like that I can inspect it in all detail...
> >
> > On 2013-06-06, at 17:51, dmacq  wrote:
> >
> > > I tried it again this morning and still had the problem.
> > >
> > > This is interesting.
> > >
> > > | x y |
> > > x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7.
> > > y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5 second: 7.
> > > x = y  <-- True
> > >
> > > But
> > > | x y |
> > > x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7.
> > > y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5 second: 7.
> > > x asTime = y asTime <- False
> > >
> > >
> > >
> > > --
> > > View this message in context: 
> > > http://forum.world.st/DateAndTime-asTime-tp4691870p4691988.html
> > > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
> > >
> >
> >
> >
> 
> 
> 

Re: [Pharo-users] ui slowness on newly installed ubuntu 13.04 64bit

[Paul DeBruicker]

I thought the profiles showed it wasn't specific to my image but happened on 
both Pharo 1.4 & 2 using a cog vm on Ubuntu 13.04 64 bit. 

On Jun 7, 2013, at 12:44 AM, Stéphane Ducasse  wrote:

> could we get the image so that we can try?
> 
> Stef
> 
> On Jun 7, 2013, at 8:27 AM, Marcus Denker  wrote:
> 
>> 
>> On Jun 6, 2013, at 5:12 PM, Paul DeBruicker  wrote:
>> 
>>> Hi Damien,
>>> 
>>> 
>>>Because of the attached Message Tally outputs I don't think the problem
>>> is specific to changes I've made to an image.  I also don't think that
>>> there is much differnece between Eliots vm or the pharo ppa vm.  The
>>> Message Tally outputs are from profiling the UI while finding the
>>> senders of #setUp using various VM & image combinations.On squeak
>>> finding the senders of #setUp seems instantaneous.On Pharo it takes
>>> multiple seconds to find and display the senders.
>>> 
>> 
>> This is really strange… here even doing "senders of" for all the >6000 
>> senders
>> of ifTrue: is quite fast for 2.0 and even faster in 3.0.
>> 
>> So I really wonder what the problem is...
>> 
>>Marcus
> 
> 

Re: [Pharo-users] DateAndTime>>asTime

[José Comesaña]

Answers in red.

Regards

2013/6/7 Sven Van Caekenberghe 

>
> On 07 Jun 2013, at 13:26, José Comesaña  wrote:
>
> > Thank you Sven.
> >
> > I had made the fixes myself, creating a new class for dates (I don't
> need the complexity of Date just for determining if a date is past, I don't
> need date arithmetic either). I just wanted to inform, mainly because the
> bug seems to be still present in Pharo 3.0.
> >
> > Anyway, your solution does not work for the 'd/m/y' pattern, although it
> does for 'd/m/yy'.
>
> Depends on what a single y means, right ?
>

According  to documentation, one y means ...year, no matter how many digits
supplied... (my own words, not litteral).  It means it will either accept
../../13 or ../../2013

>
> > I could write the tests you suggest, if you think they are interesting.
>
> Yes, please do: with a good set of tests, we can discuss using concrete
> examples.
>
>
Sure I will. Will keep you informed!


> > Regards
> >
> > 2013/6/7 Sven Van Caekenberghe 
> > Hi José,
> >
> > On 07 Jun 2013, at 12:02, José Comesaña  wrote:
> >
> > > Hello everybody.
> > >
> > > I would like to add a new improvement to this thread.
> > >
> > > I have noticed that Date class has a bug, or at least something to
> improve in readFrom:pattern: method. The initial comment states that "A
> year given using only two decimals is considered to be >2000.".
> > >
> > > But this seems to be incorrect: if you evaluate
> > >
> > > Date readFrom: '07/06/13' readStream pattern: 'd/m/y'
> > >
> > > you get:
> > >
> > >  7 June 0013 instead of  7 June 2013.
> > >
> > > I am working with version #20605
> >
> > The fix would be quite easy:
> >
> >   year := (inputStream next: 2) asInteger
> >
> > should be
> >
> >   year := 2000 + (inputStream next: 2) asInteger
> >
> > A more important problem is that there are no users of
> #readFrom:pattern: in the system, not even unit tests. If we want to keep
> the methods, someone should start by writing a couple of unit tests.
> >
> > Sven
> >
> > > Thank you all for your great work.
> > >
> > > Regards.
> > >
> > >
> > > 2013/6/6 Camillo Bruni 
> > > can you save an image with the inspector opened on both x and y, x
> asTime and y asTime
> > > and provide a link to it? like that I can inspect it in all detail...
> > >
> > > On 2013-06-06, at 17:51, dmacq  wrote:
> > >
> > > > I tried it again this morning and still had the problem.
> > > >
> > > > This is interesting.
> > > >
> > > > | x y |
> > > > x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7.
> > > > y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5
> second: 7.
> > > > x = y  <-- True
> > > >
> > > > But
> > > > | x y |
> > > > x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7.
> > > > y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5
> second: 7.
> > > > x asTime = y asTime <- False
> > > >
> > > >
> > > >
> > > > --
> > > > View this message in context:
> http://forum.world.st/DateAndTime-asTime-tp4691870p4691988.html
> > > > Sent from the Pharo Smalltalk Users mailing list archive at
> Nabble.com.
> > > >
> > >
> > >
> > >
> >
> >
> >
>
>
>

Re: [Pharo-users] DateAndTime>>asTime

[Sven Van Caekenberghe]

On 07 Jun 2013, at 14:28, José Comesaña  wrote:

> Answers in red.
> 
> Regards
> 
> 2013/6/7 Sven Van Caekenberghe 
> 
> On 07 Jun 2013, at 13:26, José Comesaña  wrote:
> 
> > Thank you Sven.
> >
> > I had made the fixes myself, creating a new class for dates (I don't need 
> > the complexity of Date just for determining if a date is past, I don't need 
> > date arithmetic either). I just wanted to inform, mainly because the bug 
> > seems to be still present in Pharo 3.0.
> >
> > Anyway, your solution does not work for the 'd/m/y' pattern, although it 
> > does for 'd/m/yy'.
> 
> Depends on what a single y means, right ?
> 
> According  to documentation, one y means ...year, no matter how many digits 
> supplied... (my own words, not litteral).  It means it will either accept 
> ../../13 or ../../2013

Yes, that is how I understood it as well. My change adds 2000 only in the case 
of 2 y's unless I am mistaken. But I must admin I didn't test it.

> > I could write the tests you suggest, if you think they are interesting.
> 
> Yes, please do: with a good set of tests, we can discuss using concrete 
> examples.
> 
> 
> Sure I will. Will keep you informed!

Super.

> > Regards
> >
> > 2013/6/7 Sven Van Caekenberghe 
> > Hi José,
> >
> > On 07 Jun 2013, at 12:02, José Comesaña  wrote:
> >
> > > Hello everybody.
> > >
> > > I would like to add a new improvement to this thread.
> > >
> > > I have noticed that Date class has a bug, or at least something to 
> > > improve in readFrom:pattern: method. The initial comment states that "A 
> > > year given using only two decimals is considered to be >2000.".
> > >
> > > But this seems to be incorrect: if you evaluate
> > >
> > > Date readFrom: '07/06/13' readStream pattern: 'd/m/y'
> > >
> > > you get:
> > >
> > >  7 June 0013 instead of  7 June 2013.
> > >
> > > I am working with version #20605
> >
> > The fix would be quite easy:
> >
> >   year := (inputStream next: 2) asInteger
> >
> > should be
> >
> >   year := 2000 + (inputStream next: 2) asInteger
> >
> > A more important problem is that there are no users of #readFrom:pattern: 
> > in the system, not even unit tests. If we want to keep the methods, someone 
> > should start by writing a couple of unit tests.
> >
> > Sven
> >
> > > Thank you all for your great work.
> > >
> > > Regards.
> > >
> > >
> > > 2013/6/6 Camillo Bruni 
> > > can you save an image with the inspector opened on both x and y, x asTime 
> > > and y asTime
> > > and provide a link to it? like that I can inspect it in all detail...
> > >
> > > On 2013-06-06, at 17:51, dmacq  wrote:
> > >
> > > > I tried it again this morning and still had the problem.
> > > >
> > > > This is interesting.
> > > >
> > > > | x y |
> > > > x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7.
> > > > y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5 second: 
> > > > 7.
> > > > x = y  <-- True
> > > >
> > > > But
> > > > | x y |
> > > > x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7.
> > > > y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5 second: 
> > > > 7.
> > > > x asTime = y asTime <- False
> > > >
> > > >
> > > >
> > > > --
> > > > View this message in context: 
> > > > http://forum.world.st/DateAndTime-asTime-tp4691870p4691988.html
> > > > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
> > > >
> > >
> > >
> > >
> >
> >
> >
> 
> 
> 

Re: [Pharo-users] Changes-File & caching

[Sean P. DeNigris]

Marcus Denker-4 wrote
> Normally I thought that fogbugz should send you updates on bugs you
> reported?
> We need to check that.

There's a plugin [1] but it requires the user to enable the preference.
Maybe there's a way to enable globally by default...

[1] http://forum.world.st/Auto-Subscribe-in-Fogbugz-td4690614.html



-
Cheers,
Sean
--
View this message in context: 
http://forum.world.st/Changes-File-caching-tp4692080p4692174.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Re: [Pharo-users] account search

[Sean P. DeNigris]

Camillo Bruni-3 wrote
> who is 

> remove@

>   on fogbugz?

I thought maybe it was Benjamin since he disappeared from the user list...



-
Cheers,
Sean
--
View this message in context: 
http://forum.world.st/account-search-tp4692121p4692176.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Re: [Pharo-users] ui slowness on newly installed ubuntu 13.04 64bit

[Paul DeBruicker]

For the attached profile I downloaded a new pharo 20606 image and ran
the search for senders of #ifTrue: twice.  It shows that it took 17
seconds on Ubuntu 13.04 64bit.  How long does it take on your machine?






On 06/06/2013 11:27 PM, Marcus Denker wrote:
> 
> On Jun 6, 2013, at 5:12 PM, Paul DeBruicker  wrote:
> 
>> Hi Damien,
>>
>>
>>  Because of the attached Message Tally outputs I don't think the problem
>> is specific to changes I've made to an image.  I also don't think that
>> there is much differnece between Eliots vm or the pharo ppa vm.  The
>> Message Tally outputs are from profiling the UI while finding the
>> senders of #setUp using various VM & image combinations.On squeak
>> finding the senders of #setUp seems instantaneous.On Pharo it takes
>> multiple seconds to find and display the senders.
>>
> 
> This is really strange… here even doing "senders of" for all the >6000 senders
> of ifTrue: is quite fast for 2.0 and even faster in 3.0.
> 
> So I really wonder what the problem is...
> 
>   Marcus
> 

 - 23840 tallies, 23876 msec.

**Tree**

Process: other processes

18.9% {4513ms} ProcessorScheduler class>>idleProcess
1.4% {337ms} WeakArray class>>finalizationProcess
  1.3% {302ms} primitives

Process: (40s) Morphic UI process: nil

71.2% {16998ms} NautilusUI(AbstractNautilusUI)>>browseSendersOfMessages
  71.2% {16998ms} NautilusUI(AbstractTool)>>browseSendersOfMessagesFrom:
70.5% {16821ms} 
NautilusUI(AbstractTool)>>getSelectorAndSendQuery:to:with:selector:
  70.5% {16821ms} SystemNavigation>>browseAllCallsOn:
70.5% {16821ms} SystemNavigation>>browseAllSendersOf:
  34.2% {8160ms} OrderedCollection(Collection)>>asSortedCollection
|34.2% {8160ms} OrderedCollection(Object)>>as:
|  34.2% {8160ms} SortedCollection class(OrderedCollection 
class)>>newFrom:
|34.2% {8160ms} SortedCollection>>addAll:
|  34.2% {8160ms} SortedCollection>>reSort
|34.2% {8160ms} SortedCollection>>sort:to:
|  34.2% {8160ms} SortedCollection>>defaultSort:to:
|34.1% {8152ms} SortedCollection>>defaultSort:to:
|  34.1% {8134ms} SortedCollection>>defaultSort:to:
|33.9% {8104ms} SortedCollection>>defaultSort:to:
|  33.6% {8024ms} SortedCollection>>defaultSort:to:
|33.2% {7920ms} 
SortedCollection>>defaultSort:to:
|  32.5% {7770ms} 
SortedCollection>>defaultSort:to:
|31.4% {7507ms} 
SortedCollection>>defaultSort:to:
|  |30.0% {7163ms} 
SortedCollection>>defaultSort:to:
|  |  |27.3% {6520ms} 
SortedCollection>>defaultSort:to:
|  |  |  |22.5% {5376ms} 
SortedCollection>>defaultSort:to:
|  |  |  |  |15.8% {3784ms} 
SortedCollection>>defaultSort:to:
|  |  |  |  |  |8.6% {2059ms} 
SortedCollection>>defaultSort:to:
|  |  |  |  |  |  |4.7% {1122ms} 
RGMethodDefinition>><=
|  |  |  |  |  |  |  |4.1% {975ms} 
RGMethodDefinition>>timeStamp
|  |  |  |  |  |  |  |  3.0% {715ms} 
RGMethodDefinition>>stamp
|  |  |  |  |  |  |  |2.9% {687ms} 
CompiledMethod>>timeStamp
|  |  |  |  |  |  |  |  1.9% {457ms} 
CompiledMethod>>timeStampFromFile:
|  |  |  |  |  |  |  |1.7% {397ms} 
Scanner>>scanTokens:
|  |  |  |  |  |  |  |  1.6% 
{375ms} Scanner>>scanLitVec
|  |  |  |  |  |  |  |1.5% 
{349ms} Scanner>>scanToken
|  |  |  |  |  |  |  |  1.4% 
{326ms} Character>>asSymbol
|  |  |  |  |  |  |  |1.4% 
{326ms} Symbol class>>internCharacter:
|  |  |  |  |  |  |  |  
1.4% {324ms} Symbol class>>intern:
|  |  |  |  |  |  |  |
1.3% {320ms} Symbol class>>lookup:
|  |  |  |  |  |  |  |  
1.3% {320ms} WeakSet>>like:
|  |  |  |  |  |  |  |  
  1.3% {320ms} WeakSet>>scanFor:
|  |  |  |  |  |  |3.9% {929ms} 
SortedCollection>>defaultSort:to:
|  |  |  |  |  |  |  2.2% {533ms} 
RGMethodDefinition>><=
|

Re: [Pharo-users] DateAndTime>>asTime

[Stéphane Ducasse]

can you open a bug entry and publish a slice so that we do not fix it.

Stef

On Jun 7, 2013, at 12:36 PM, Sven Van Caekenberghe  wrote:

> Hi José,
> 
> On 07 Jun 2013, at 12:02, José Comesaña  wrote:
> 
>> Hello everybody. 
>> 
>> I would like to add a new improvement to this thread.
>> 
>> I have noticed that Date class has a bug, or at least something to improve 
>> in readFrom:pattern: method. The initial comment states that "A year given 
>> using only two decimals is considered to be >2000.". 
>> 
>> But this seems to be incorrect: if you evaluate 
>> 
>> Date readFrom: '07/06/13' readStream pattern: 'd/m/y'
>> 
>> you get:
>> 
>> 7 June 0013 instead of  7 June 2013.
>> 
>> I am working with version #20605
> 
> The fix would be quite easy:
> 
>  year := (inputStream next: 2) asInteger
> 
> should be
> 
>  year := 2000 + (inputStream next: 2) asInteger
> 
> A more important problem is that there are no users of #readFrom:pattern: in 
> the system, not even unit tests. If we want to keep the methods, someone 
> should start by writing a couple of unit tests.
> 
> Sven
> 
>> Thank you all for your great work.
>> 
>> Regards.
>> 
>> 
>> 2013/6/6 Camillo Bruni 
>> can you save an image with the inspector opened on both x and y, x asTime 
>> and y asTime
>> and provide a link to it? like that I can inspect it in all detail...
>> 
>> On 2013-06-06, at 17:51, dmacq  wrote:
>> 
>>> I tried it again this morning and still had the problem.
>>> 
>>> This is interesting.
>>> 
>>> | x y |
>>> x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7.
>>> y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5 second: 7.
>>> x = y  <-- True
>>> 
>>> But
>>> | x y |
>>> x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7.
>>> y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5 second: 7.
>>> x asTime = y asTime <- False
>>> 
>>> 
>>> 
>>> --
>>> View this message in context: 
>>> http://forum.world.st/DateAndTime-asTime-tp4691870p4691988.html
>>> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
>>> 
>> 
>> 
>> 
> 
> 

Re: [Pharo-users] DateAndTime>>asTime

[Stéphane Ducasse]

>> 
>> 
>> I had made the fixes myself, creating a new class for dates (I don't need 
>> the complexity of Date just for determining if a date is past, I don't need 
>> date arithmetic either). I just wanted to inform, mainly because the bug 
>> seems to be still present in Pharo 3.0.
>> 
>> Anyway, your solution does not work for the 'd/m/y' pattern, although it 
>> does for 'd/m/yy'.
> 
> Depends on what a single y means, right ?
> 
>> I could write the tests you suggest, if you think they are interesting. 
> 
> Yes, please do: with a good set of tests, we can discuss using concrete 
> examples. 

Please :)
We love tests!

Re: [Pharo-users] ui slowness on newly installed ubuntu 13.04 64bit

[Sven Van Caekenberghe]

On 07 Jun 2013, at 15:44, Paul DeBruicker  wrote:

> For the attached profile I downloaded a new pharo 20606 image and ran
> the search for senders of #ifTrue: twice.  It shows that it took 17
> seconds on Ubuntu 13.04 64bit.  How long does it take on your machine?

[ SystemNavigation new allSendersOf: #ifTrue: ] timeToRun   =>>  258 
"milliseconds"

I feel for you, Paul, this is really annoying...

> On 06/06/2013 11:27 PM, Marcus Denker wrote:
>> 
>> On Jun 6, 2013, at 5:12 PM, Paul DeBruicker  wrote:
>> 
>>> Hi Damien,
>>> 
>>> 
>>> Because of the attached Message Tally outputs I don't think the problem
>>> is specific to changes I've made to an image.  I also don't think that
>>> there is much differnece between Eliots vm or the pharo ppa vm.  The
>>> Message Tally outputs are from profiling the UI while finding the
>>> senders of #setUp using various VM & image combinations.On squeak
>>> finding the senders of #setUp seems instantaneous.On Pharo it takes
>>> multiple seconds to find and display the senders.
>>> 
>> 
>> This is really strange… here even doing "senders of" for all the >6000 
>> senders
>> of ifTrue: is quite fast for 2.0 and even faster in 3.0.
>> 
>> So I really wonder what the problem is...
>> 
>>  Marcus
>> 
> 
> 

Re: [Pharo-users] ui slowness on newly installed ubuntu 13.04 64bit

[Marcus Denker]

On Jun 7, 2013, at 3:45 PM, Paul DeBruicker  wrote:

> For the attached profile I downloaded a new pharo 20606 image and ran
> the search for senders of #ifTrue: twice.  It shows that it took 17
> seconds on Ubuntu 13.04 64bit.  How long does it take on your machine?
> 

[SystemNavigation new browseMessageList: (SystemNavigation new  allCallsOn: 
#ifTrue:) name: 'Senders or Users of ', #ifTrue: autoSelect: #ifTrue: ] 
timeToRun

->> 743

0.7 seconds.

out of that, 

[SystemNavigation new allCallsOn: #ifTrue: ] timeToRun

takes ca. 0.11 seconds.

Re: [Pharo-users] ui slowness on newly installed ubuntu 13.04 64bit

[Camillo Bruni]

On 2013-06-07, at 16:03, Marcus Denker  wrote:

> 
> On Jun 7, 2013, at 3:45 PM, Paul DeBruicker  wrote:
> 
>> For the attached profile I downloaded a new pharo 20606 image and ran
>> the search for senders of #ifTrue: twice.  It shows that it took 17
>> seconds on Ubuntu 13.04 64bit.  How long does it take on your machine?

On my virtualbox ubuntu 13.04 

[SystemNavigation new allCallsOn: #ifTrue: ] timeToRun == 1052

:/

Re: [Pharo-users] ui slowness on newly installed ubuntu 13.04 64bit

[Goubier Thierry]

Le 07/06/2013 16:00, Sven Van Caekenberghe a écrit :


On 07 Jun 2013, at 15:44, Paul DeBruicker  wrote:


For the attached profile I downloaded a new pharo 20606 image and ran
the search for senders of #ifTrue: twice.  It shows that it took 17
seconds on Ubuntu 13.04 64bit.  How long does it take on your machine?


[ SystemNavigation new allSendersOf: #ifTrue: ] timeToRun   =>>  258 
"milliseconds"


20606, Ubuntu 13.04 64bits, Core i3-2350M CPU @ 2.30GHz
[ SystemNavigation new allSendersOf: #ifTrue: ] timeToRun =>> [292, 330] ms

Thierry
--
Thierry Goubier
CEA list
Laboratoire des Fondations des Systèmes Temps Réel Embarqués
91191 Gif sur Yvette Cedex
France
Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

[Pharo-users] Pharo on Raspberry Pi

[Tony Giaccone]

I recently got a Raspberry Pi and was pleasantly surprised to see that 
smalltalk is part of the image. I quickly did a search to see if Pharo was 
available. While there was a flurry of messages about getting a version that 
would work on the. Pi. I haven't seem anything saying it had happened.

Is it possible to run Pharo on my RaspPi?

Re: [Pharo-users] Pharo on Raspberry Pi

[Sven Van Caekenberghe]

Tony,

On 07 Jun 2013, at 16:52, Tony Giaccone  wrote:

> I recently got a Raspberry Pi and was pleasantly surprised to see that 
> smalltalk is part of the image. I quickly did a search to see if Pharo was 
> available. While there was a flurry of messages about getting a version that 
> would work on the. Pi. I haven't seem anything saying it had happened.
> 
> Is it possible to run Pharo on my RaspPi?

Short answer: yes you can but only older versions (I think 1.4) since newer 
version (2.0 and up) depend on extra primitives in the VM (for FileSystem, 
Data/Time stuff). The VM on the RPi is quite old and there is not specific 
Pharo VM (yet).

Sven

Re: [Pharo-users] ui slowness on newly installed ubuntu 13.04 64bit

[Paul DeBruicker]

My laptop is:

[SystemNavigation new allCallsOn: #ifTrue: ] timeToRun 1518



On 06/07/2013 07:07 AM, Camillo Bruni wrote:
> 
> On 2013-06-07, at 16:03, Marcus Denker  wrote:
> 
>>
>> On Jun 7, 2013, at 3:45 PM, Paul DeBruicker  wrote:
>>
>>> For the attached profile I downloaded a new pharo 20606 image and ran
>>> the search for senders of #ifTrue: twice.  It shows that it took 17
>>> seconds on Ubuntu 13.04 64bit.  How long does it take on your machine?
> 
> On my virtualbox ubuntu 13.04 
> 
> [SystemNavigation new allCallsOn: #ifTrue: ] timeToRun == 1052
> 
> :/
> 

Re: [Pharo-users] ui slowness on newly installed ubuntu 13.04 64bit

[Paul DeBruicker]

Sounds like I need some new hardware then?




On 06/07/2013 07:16 AM, Goubier Thierry wrote:
> 
> 
> Le 07/06/2013 16:00, Sven Van Caekenberghe a écrit :
>>
>> On 07 Jun 2013, at 15:44, Paul DeBruicker  wrote:
>>
>>> For the attached profile I downloaded a new pharo 20606 image and ran
>>> the search for senders of #ifTrue: twice.  It shows that it took 17
>>> seconds on Ubuntu 13.04 64bit.  How long does it take on your machine?
>>
>> [ SystemNavigation new allSendersOf: #ifTrue: ] timeToRun   =>>  258
>> "milliseconds"
> 
> 20606, Ubuntu 13.04 64bits, Core i3-2350M CPU @ 2.30GHz
> [ SystemNavigation new allSendersOf: #ifTrue: ] timeToRun =>> [292, 330] ms
> 
> Thierry

Re: [Pharo-users] ui slowness on newly installed ubuntu 13.04 64bit

[Goubier Thierry]

I'll check with some older hardware; I have something slower than yours, 
but I'll have the results later tonight.


Thierry

Le 07/06/2013 17:04, Paul DeBruicker a écrit :

Sounds like I need some new hardware then?




On 06/07/2013 07:16 AM, Goubier Thierry wrote:



Le 07/06/2013 16:00, Sven Van Caekenberghe a écrit :


On 07 Jun 2013, at 15:44, Paul DeBruicker  wrote:


For the attached profile I downloaded a new pharo 20606 image and ran
the search for senders of #ifTrue: twice.  It shows that it took 17
seconds on Ubuntu 13.04 64bit.  How long does it take on your machine?


[ SystemNavigation new allSendersOf: #ifTrue: ] timeToRun   =>>  258
"milliseconds"


20606, Ubuntu 13.04 64bits, Core i3-2350M CPU @ 2.30GHz
[ SystemNavigation new allSendersOf: #ifTrue: ] timeToRun =>> [292, 330] ms

Thierry







--
Thierry Goubier
CEA list
Laboratoire des Fondations des Systèmes Temps Réel Embarqués
91191 Gif sur Yvette Cedex
France
Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Re: [Pharo-users] ui slowness on newly installed ubuntu 13.04 64bit

[Marcus Denker]

On Jun 7, 2013, at 5:04 PM, Paul DeBruicker  wrote:

> My laptop is:
> 
> [SystemNavigation new allCallsOn: #ifTrue: ] timeToRun 1518
> 
> 
(3.0):
[SystemNavigation new allCallsOn: #ifTrue: ] timeToRun 117

I have a slow machine: 1.8Ghz Core i5 in a MacBook Air.
It auto-overclocks to 2.8 Ghz when not using two cores.

It's supposed to be not a fast system, as far as I understood. 

Marcus

Re: [Pharo-users] ui slowness on newly installed ubuntu 13.04 64bit

[Paul DeBruicker]

OK.  I'm going to check on a 12.04 vm and windows xp vm on this hardware
right now.  I'll report back in a bit






On 06/07/2013 08:13 AM, Goubier Thierry wrote:
> I'll check with some older hardware; I have something slower than yours,
> but I'll have the results later tonight.
> 
> Thierry
> 
> Le 07/06/2013 17:04, Paul DeBruicker a écrit :
>> Sounds like I need some new hardware then?
>>
>>
>>
>>
>> On 06/07/2013 07:16 AM, Goubier Thierry wrote:
>>>
>>>
>>> Le 07/06/2013 16:00, Sven Van Caekenberghe a écrit :

 On 07 Jun 2013, at 15:44, Paul DeBruicker  wrote:

> For the attached profile I downloaded a new pharo 20606 image and ran
> the search for senders of #ifTrue: twice.  It shows that it took 17
> seconds on Ubuntu 13.04 64bit.  How long does it take on your machine?

 [ SystemNavigation new allSendersOf: #ifTrue: ] timeToRun   =>>  258
 "milliseconds"
>>>
>>> 20606, Ubuntu 13.04 64bits, Core i3-2350M CPU @ 2.30GHz
>>> [ SystemNavigation new allSendersOf: #ifTrue: ] timeToRun =>> [292,
>>> 330] ms
>>>
>>> Thierry
>>
>>
>>
>>
> 

Re: [Pharo-users] ui slowness on newly installed ubuntu 13.04 64bit

[Camillo Bruni]

Can you try on the command line only?

curl get.pharo.org/30+vm | bash
./pharo Pharo.image eval "[SystemNavigation new allCallsOn: #ifTrue: ] 
timeToRun"



On 2013-06-07, at 17:12, Marcus Denker  wrote:

> 
> On Jun 7, 2013, at 5:04 PM, Paul DeBruicker  wrote:
> 
>> My laptop is:
>> 
>> [SystemNavigation new allCallsOn: #ifTrue: ] timeToRun 1518
>> 
>> 
> (3.0):
> [SystemNavigation new allCallsOn: #ifTrue: ] timeToRun 117
> 
> I have a slow machine: 1.8Ghz Core i5 in a MacBook Air.
> It auto-overclocks to 2.8 Ghz when not using two cores.
> 
> It's supposed to be not a fast system, as far as I understood. 
> 
>   Marcus
> 
> 

Re: [Pharo-users] ui slowness on newly installed ubuntu 13.04 64bit

[Paul DeBruicker]

>From the below it seems to be something with running on linux 64bits
with a UI slows it down by a factor of 10x.


Command line per Camillo below on ubuntu 13.04 64bit on the hardware
was: 134ms

Using Pharo-2 windows all in one on a windows xp virtualbox VM was: 163ms

Using Pharo-2 linux all in one on a ubuntu 12,04 64bit virtualbox VM
was: 1918ms


Using Pharo-2 linux all in one on a debian 6 32bit virtualbox VM was: 152 ms






On 06/07/2013 08:15 AM, Camillo Bruni wrote:
> Can you try on the command line only?
> 
> curl get.pharo.org/30+vm | bash
> ./pharo Pharo.image eval "[SystemNavigation new allCallsOn: #ifTrue: ] 
> timeToRun"
> 
> 
> 
> On 2013-06-07, at 17:12, Marcus Denker  wrote:
> 
>>
>> On Jun 7, 2013, at 5:04 PM, Paul DeBruicker  wrote:
>>
>>> My laptop is:
>>>
>>> [SystemNavigation new allCallsOn: #ifTrue: ] timeToRun 1518
>>>
>>>
>> (3.0):
>> [SystemNavigation new allCallsOn: #ifTrue: ] timeToRun 117
>>
>> I have a slow machine: 1.8Ghz Core i5 in a MacBook Air.
>> It auto-overclocks to 2.8 Ghz when not using two cores.
>>
>> It's supposed to be not a fast system, as far as I understood. 
>>
>>  Marcus
>>
>>
> 
> 

Re: [Pharo-users] ui slowness on newly installed ubuntu 13.04 64bit

[Markus Fritsche]

On 07.06.2013 17:55, Paul DeBruicker wrote:

 From the below it seems to be something with running on linux 64bits
with a UI slows it down by a factor of 10x.


Command line per Camillo below on ubuntu 13.04 64bit on the hardware
was: 134ms

Using Pharo-2 windows all in one on a windows xp virtualbox VM was: 163ms

Using Pharo-2 linux all in one on a ubuntu 12,04 64bit virtualbox VM
was: 1918ms


Using Pharo-2 linux all in one on a debian 6 32bit virtualbox VM was: 152 ms

Further research:
Pharo PPA VM, Ubuntu 13.04 64Bit:
[SystemNavigation new allCallsOn: #ifTrue: ] timeToRun 2230
CogVM from Eliot directly ( 
http://www.mirandabanda.org/files/Cog/VM/VM.r2732/):

[SystemNavigation new allCallsOn: #ifTrue: ] timeToRun 164

Kind regards,
   Markus

Re: [Pharo-users] ui slowness on newly installed ubuntu 13.04 64bit

[Paul DeBruicker]

And the pharo2 linux all-in-one runs in 116ms on my hardware on Ubuntu
13.04 64bit.





On 06/07/2013 09:35 AM, Markus Fritsche wrote:
> On 07.06.2013 17:55, Paul DeBruicker wrote:
>> From the below it seems to be something with running on linux 64bits
>> with a UI slows it down by a factor of 10x.
>>
>>
>> Command line per Camillo below on ubuntu 13.04 64bit on the hardware
>> was: 134ms
>>
>> Using Pharo-2 windows all in one on a windows xp virtualbox VM was: 163ms
>>
>> Using Pharo-2 linux all in one on a ubuntu 12,04 64bit virtualbox VM
>> was: 1918ms
>>
>>
>> Using Pharo-2 linux all in one on a debian 6 32bit virtualbox VM was: 152 ms
> Further research:
> Pharo PPA VM, Ubuntu 13.04 64Bit:
> [SystemNavigation new allCallsOn: #ifTrue: ] timeToRun 2230
> CogVM from Eliot directly (
> http://www.mirandabanda.org/files/Cog/VM/VM.r2732/):
> [SystemNavigation new allCallsOn: #ifTrue: ] timeToRun 164
> 
> Kind regards,
>Markus

Re: [Pharo-users] Changes-File & caching

[Stéphane Ducasse]

On Jun 7, 2013, at 11:14 AM, Sven Van Caekenberghe  wrote:

> 
> On 07 Jun 2013, at 11:07, Markus Fritsche  wrote:
> 
>> Hello Sven & List,
>> 
>> On 07.06.2013 10:45, Sven Van Caekenberghe wrote:
>>> Yes, it is an important problem (but the trigger is a change in Ubuntu 
>>> 13.04). I am not an Ubuntu desktop user, I can only hope that those who are 
>>> will help.
>> Well, I have 13.04 on a few laptops (2GB Atom netbook, 8GB i7 dual core and 
>> 6GB AMD 4Core) with different file systems (ext4, btrfs) on them, so I have 
>> quite a few configurations at hand to test with.
> 
> Great, we need more Linux Desktop users, the community it too Mac centric ;-)

+1
I'm waiting that mac gets totally evil to switch :)

>> The RemoteString-Error during updates has been fixed; as I see the files 
>> referenced by the download links have been replaced. The only "old" image 
>> left I found was the one titled "Pharo 2.0 image" on 
>> http://www.pharo-project.org/pharo-download which raises the error in 
>> ScriptLoaderupdate>>#20605
> 
> We need to fix that then.
> 
> Thanks for the feedback.
> 
> Sven
> 
> --
> Sven Van Caekenberghe
> Proudly supporting Pharo
> http://pharo.org
> http://association.pharo.org
> http://consortium.pharo.org
> 
> 
> 
> 
> 

Re: [Pharo-users] DateAndTime>>asTime

[José Comesaña]

Hi again.

I have one first test for #readFrom:pattern:. What can I do now to send it,
where, to whom?.

Regards

2013/6/7 Sven Van Caekenberghe 

>
> On 07 Jun 2013, at 14:28, José Comesaña  wrote:
>
> > Answers in red.
> >
> > Regards
> >
> > 2013/6/7 Sven Van Caekenberghe 
> >
> > On 07 Jun 2013, at 13:26, José Comesaña  wrote:
> >
> > > Thank you Sven.
> > >
> > > I had made the fixes myself, creating a new class for dates (I don't
> need the complexity of Date just for determining if a date is past, I don't
> need date arithmetic either). I just wanted to inform, mainly because the
> bug seems to be still present in Pharo 3.0.
> > >
> > > Anyway, your solution does not work for the 'd/m/y' pattern, although
> it does for 'd/m/yy'.
> >
> > Depends on what a single y means, right ?
> >
> > According  to documentation, one y means ...year, no matter how many
> digits supplied... (my own words, not litteral).  It means it will either
> accept ../../13 or ../../2013
>
> Yes, that is how I understood it as well. My change adds 2000 only in the
> case of 2 y's unless I am mistaken. But I must admin I didn't test it.
>
> > > I could write the tests you suggest, if you think they are interesting.
> >
> > Yes, please do: with a good set of tests, we can discuss using concrete
> examples.
> >
> >
> > Sure I will. Will keep you informed!
>
> Super.
>
> > > Regards
> > >
> > > 2013/6/7 Sven Van Caekenberghe 
> > > Hi José,
> > >
> > > On 07 Jun 2013, at 12:02, José Comesaña 
> wrote:
> > >
> > > > Hello everybody.
> > > >
> > > > I would like to add a new improvement to this thread.
> > > >
> > > > I have noticed that Date class has a bug, or at least something to
> improve in readFrom:pattern: method. The initial comment states that "A
> year given using only two decimals is considered to be >2000.".
> > > >
> > > > But this seems to be incorrect: if you evaluate
> > > >
> > > > Date readFrom: '07/06/13' readStream pattern: 'd/m/y'
> > > >
> > > > you get:
> > > >
> > > >  7 June 0013 instead of  7 June 2013.
> > > >
> > > > I am working with version #20605
> > >
> > > The fix would be quite easy:
> > >
> > >   year := (inputStream next: 2) asInteger
> > >
> > > should be
> > >
> > >   year := 2000 + (inputStream next: 2) asInteger
> > >
> > > A more important problem is that there are no users of
> #readFrom:pattern: in the system, not even unit tests. If we want to keep
> the methods, someone should start by writing a couple of unit tests.
> > >
> > > Sven
> > >
> > > > Thank you all for your great work.
> > > >
> > > > Regards.
> > > >
> > > >
> > > > 2013/6/6 Camillo Bruni 
> > > > can you save an image with the inspector opened on both x and y, x
> asTime and y asTime
> > > > and provide a link to it? like that I can inspect it in all detail...
> > > >
> > > > On 2013-06-06, at 17:51, dmacq  wrote:
> > > >
> > > > > I tried it again this morning and still had the problem.
> > > > >
> > > > > This is interesting.
> > > > >
> > > > > | x y |
> > > > > x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7.
> > > > > y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5
> second: 7.
> > > > > x = y  <-- True
> > > > >
> > > > > But
> > > > > | x y |
> > > > > x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7.
> > > > > y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5
> second: 7.
> > > > > x asTime = y asTime <- False
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > View this message in context:
> http://forum.world.st/DateAndTime-asTime-tp4691870p4691988.html
> > > > > Sent from the Pharo Smalltalk Users mailing list archive at
> Nabble.com.
> > > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
> >
> >
>
>
>

Re: [Pharo-users] Pharo on Raspberry Pi

[btc]

Tony Giaccone wrote:

I recently got a Raspberry Pi and was pleasantly surprised to see that 
smalltalk is part of the image. I quickly did a search to see if Pharo was 
available. While there was a flurry of messages about getting a version that 
would work on the. Pi. I haven't seem anything saying it had happened.

Is it possible to run Pharo on my RaspPi?

  
You didn't say which smalltalk was there, so I'll just mention that Tim 
Rowledge on [squeak-dev] list appears to have Squeak running on the RaspPi.


cheers -ben

Re: [Pharo-users] DateAndTime>>asTime

[Stéphane Ducasse]

> Hi again.
> 
> I have one first test for #readFrom:pattern:. What can I do now to send it, 
> where, to whom?.

I will create a bug entry for you and you create a slice with the test and the 
fix and you publish it in the pharo inbox.

Stef

> 
> Regards
> 
> 2013/6/7 Sven Van Caekenberghe 
> 
> On 07 Jun 2013, at 14:28, José Comesaña  wrote:
> 
> > Answers in red.
> >
> > Regards
> >
> > 2013/6/7 Sven Van Caekenberghe 
> >
> > On 07 Jun 2013, at 13:26, José Comesaña  wrote:
> >
> > > Thank you Sven.
> > >
> > > I had made the fixes myself, creating a new class for dates (I don't need 
> > > the complexity of Date just for determining if a date is past, I don't 
> > > need date arithmetic either). I just wanted to inform, mainly because the 
> > > bug seems to be still present in Pharo 3.0.
> > >
> > > Anyway, your solution does not work for the 'd/m/y' pattern, although it 
> > > does for 'd/m/yy'.
> >
> > Depends on what a single y means, right ?
> >
> > According  to documentation, one y means ...year, no matter how many digits 
> > supplied... (my own words, not litteral).  It means it will either accept 
> > ../../13 or ../../2013
> 
> Yes, that is how I understood it as well. My change adds 2000 only in the 
> case of 2 y's unless I am mistaken. But I must admin I didn't test it.
> 
> > > I could write the tests you suggest, if you think they are interesting.
> >
> > Yes, please do: with a good set of tests, we can discuss using concrete 
> > examples.
> >
> >
> > Sure I will. Will keep you informed!
> 
> Super.
> 
> > > Regards
> > >
> > > 2013/6/7 Sven Van Caekenberghe 
> > > Hi José,
> > >
> > > On 07 Jun 2013, at 12:02, José Comesaña  wrote:
> > >
> > > > Hello everybody.
> > > >
> > > > I would like to add a new improvement to this thread.
> > > >
> > > > I have noticed that Date class has a bug, or at least something to 
> > > > improve in readFrom:pattern: method. The initial comment states that "A 
> > > > year given using only two decimals is considered to be >2000.".
> > > >
> > > > But this seems to be incorrect: if you evaluate
> > > >
> > > > Date readFrom: '07/06/13' readStream pattern: 'd/m/y'
> > > >
> > > > you get:
> > > >
> > > >  7 June 0013 instead of  7 June 2013.
> > > >
> > > > I am working with version #20605
> > >
> > > The fix would be quite easy:
> > >
> > >   year := (inputStream next: 2) asInteger
> > >
> > > should be
> > >
> > >   year := 2000 + (inputStream next: 2) asInteger
> > >
> > > A more important problem is that there are no users of #readFrom:pattern: 
> > > in the system, not even unit tests. If we want to keep the methods, 
> > > someone should start by writing a couple of unit tests.
> > >
> > > Sven
> > >
> > > > Thank you all for your great work.
> > > >
> > > > Regards.
> > > >
> > > >
> > > > 2013/6/6 Camillo Bruni 
> > > > can you save an image with the inspector opened on both x and y, x 
> > > > asTime and y asTime
> > > > and provide a link to it? like that I can inspect it in all detail...
> > > >
> > > > On 2013-06-06, at 17:51, dmacq  wrote:
> > > >
> > > > > I tried it again this morning and still had the problem.
> > > > >
> > > > > This is interesting.
> > > > >
> > > > > | x y |
> > > > > x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7.
> > > > > y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5 
> > > > > second: 7.
> > > > > x = y  <-- True
> > > > >
> > > > > But
> > > > > | x y |
> > > > > x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7.
> > > > > y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5 
> > > > > second: 7.
> > > > > x asTime = y asTime <- False
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > View this message in context: 
> > > > > http://forum.world.st/DateAndTime-asTime-tp4691870p4691988.html
> > > > > Sent from the Pharo Smalltalk Users mailing list archive at 
> > > > > Nabble.com.
> > > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
> >
> >
> 
> 
> 

Re: [Pharo-users] DateAndTime>>asTime

[Stéphane Ducasse]

Here it is https://pharo.fogbugz.com/default.asp?10869

Stef



On Jun 7, 2013, at 8:17 PM, Stéphane Ducasse  wrote:

> 
> 
>> Hi again.
>> 
>> I have one first test for #readFrom:pattern:. What can I do now to send it, 
>> where, to whom?.
> 
> I will create a bug entry for you and you create a slice with the test and 
> the fix and you publish it in the pharo inbox.
> 
> Stef
> 
>> 
>> Regards
>> 
>> 2013/6/7 Sven Van Caekenberghe 
>> 
>> On 07 Jun 2013, at 14:28, José Comesaña  wrote:
>> 
>> > Answers in red.
>> >
>> > Regards
>> >
>> > 2013/6/7 Sven Van Caekenberghe 
>> >
>> > On 07 Jun 2013, at 13:26, José Comesaña  wrote:
>> >
>> > > Thank you Sven.
>> > >
>> > > I had made the fixes myself, creating a new class for dates (I don't 
>> > > need the complexity of Date just for determining if a date is past, I 
>> > > don't need date arithmetic either). I just wanted to inform, mainly 
>> > > because the bug seems to be still present in Pharo 3.0.
>> > >
>> > > Anyway, your solution does not work for the 'd/m/y' pattern, although it 
>> > > does for 'd/m/yy'.
>> >
>> > Depends on what a single y means, right ?
>> >
>> > According  to documentation, one y means ...year, no matter how many 
>> > digits supplied... (my own words, not litteral).  It means it will either 
>> > accept ../../13 or ../../2013
>> 
>> Yes, that is how I understood it as well. My change adds 2000 only in the 
>> case of 2 y's unless I am mistaken. But I must admin I didn't test it.
>> 
>> > > I could write the tests you suggest, if you think they are interesting.
>> >
>> > Yes, please do: with a good set of tests, we can discuss using concrete 
>> > examples.
>> >
>> >
>> > Sure I will. Will keep you informed!
>> 
>> Super.
>> 
>> > > Regards
>> > >
>> > > 2013/6/7 Sven Van Caekenberghe 
>> > > Hi José,
>> > >
>> > > On 07 Jun 2013, at 12:02, José Comesaña  wrote:
>> > >
>> > > > Hello everybody.
>> > > >
>> > > > I would like to add a new improvement to this thread.
>> > > >
>> > > > I have noticed that Date class has a bug, or at least something to 
>> > > > improve in readFrom:pattern: method. The initial comment states that 
>> > > > "A year given using only two decimals is considered to be >2000.".
>> > > >
>> > > > But this seems to be incorrect: if you evaluate
>> > > >
>> > > > Date readFrom: '07/06/13' readStream pattern: 'd/m/y'
>> > > >
>> > > > you get:
>> > > >
>> > > >  7 June 0013 instead of  7 June 2013.
>> > > >
>> > > > I am working with version #20605
>> > >
>> > > The fix would be quite easy:
>> > >
>> > >   year := (inputStream next: 2) asInteger
>> > >
>> > > should be
>> > >
>> > >   year := 2000 + (inputStream next: 2) asInteger
>> > >
>> > > A more important problem is that there are no users of 
>> > > #readFrom:pattern: in the system, not even unit tests. If we want to 
>> > > keep the methods, someone should start by writing a couple of unit tests.
>> > >
>> > > Sven
>> > >
>> > > > Thank you all for your great work.
>> > > >
>> > > > Regards.
>> > > >
>> > > >
>> > > > 2013/6/6 Camillo Bruni 
>> > > > can you save an image with the inspector opened on both x and y, x 
>> > > > asTime and y asTime
>> > > > and provide a link to it? like that I can inspect it in all detail...
>> > > >
>> > > > On 2013-06-06, at 17:51, dmacq  wrote:
>> > > >
>> > > > > I tried it again this morning and still had the problem.
>> > > > >
>> > > > > This is interesting.
>> > > > >
>> > > > > | x y |
>> > > > > x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7.
>> > > > > y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5 
>> > > > > second: 7.
>> > > > > x = y  <-- True
>> > > > >
>> > > > > But
>> > > > > | x y |
>> > > > > x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7.
>> > > > > y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5 
>> > > > > second: 7.
>> > > > > x asTime = y asTime <- False
>> > > > >
>> > > > >
>> > > > >
>> > > > > --
>> > > > > View this message in context: 
>> > > > > http://forum.world.st/DateAndTime-asTime-tp4691870p4691988.html
>> > > > > Sent from the Pharo Smalltalk Users mailing list archive at 
>> > > > > Nabble.com.
>> > > > >
>> > > >
>> > > >
>> > > >
>> > >
>> > >
>> > >
>> >
>> >
>> >
>> 
>> 
>> 
> 

Re: [Pharo-users] DateAndTime>>asTime

[José Comesaña]

Done.

I hope I have made it correctly. If not, please tell me.

Regards

2013/6/7 Stéphane Ducasse 

> Here it is https://pharo.fogbugz.com/default.asp?10869
>
> Stef
>
>
>
>
> On Jun 7, 2013, at 8:17 PM, Stéphane Ducasse 
> wrote:
>
>
>
> Hi again.
>
> I have one first test for #readFrom:pattern:. What can I do now to send
> it, where, to whom?.
>
>
> I will create a bug entry for you and you create a slice with the test and
> the fix and you publish it in the pharo inbox.
>
> Stef
>
>
> Regards
>
> 2013/6/7 Sven Van Caekenberghe 
>
>>
>> On 07 Jun 2013, at 14:28, José Comesaña  wrote:
>>
>> > Answers in red.
>> >
>> > Regards
>> >
>> > 2013/6/7 Sven Van Caekenberghe 
>> >
>> > On 07 Jun 2013, at 13:26, José Comesaña 
>> wrote:
>> >
>> > > Thank you Sven.
>> > >
>> > > I had made the fixes myself, creating a new class for dates (I don't
>> need the complexity of Date just for determining if a date is past, I don't
>> need date arithmetic either). I just wanted to inform, mainly because the
>> bug seems to be still present in Pharo 3.0.
>> > >
>> > > Anyway, your solution does not work for the 'd/m/y' pattern, although
>> it does for 'd/m/yy'.
>> >
>> > Depends on what a single y means, right ?
>> >
>> > According  to documentation, one y means ...year, no matter how many
>> digits supplied... (my own words, not litteral).  It means it will either
>> accept ../../13 or ../../2013
>>
>> Yes, that is how I understood it as well. My change adds 2000 only in the
>> case of 2 y's unless I am mistaken. But I must admin I didn't test it.
>>
>> > > I could write the tests you suggest, if you think they are
>> interesting.
>> >
>> > Yes, please do: with a good set of tests, we can discuss using concrete
>> examples.
>> >
>> >
>> > Sure I will. Will keep you informed!
>>
>> Super.
>>
>> > > Regards
>> > >
>> > > 2013/6/7 Sven Van Caekenberghe 
>> > > Hi José,
>> > >
>> > > On 07 Jun 2013, at 12:02, José Comesaña 
>> wrote:
>> > >
>> > > > Hello everybody.
>> > > >
>> > > > I would like to add a new improvement to this thread.
>> > > >
>> > > > I have noticed that Date class has a bug, or at least something to
>> improve in readFrom:pattern: method. The initial comment states that "A
>> year given using only two decimals is considered to be >2000.".
>> > > >
>> > > > But this seems to be incorrect: if you evaluate
>> > > >
>> > > > Date readFrom: '07/06/13' readStream pattern: 'd/m/y'
>> > > >
>> > > > you get:
>> > > >
>> > > >  7 June 0013 instead of  7 June 2013.
>> > > >
>> > > > I am working with version #20605
>> > >
>> > > The fix would be quite easy:
>> > >
>> > >   year := (inputStream next: 2) asInteger
>> > >
>> > > should be
>> > >
>> > >   year := 2000 + (inputStream next: 2) asInteger
>> > >
>> > > A more important problem is that there are no users of
>> #readFrom:pattern: in the system, not even unit tests. If we want to keep
>> the methods, someone should start by writing a couple of unit tests.
>> > >
>> > > Sven
>> > >
>> > > > Thank you all for your great work.
>> > > >
>> > > > Regards.
>> > > >
>> > > >
>> > > > 2013/6/6 Camillo Bruni 
>> > > > can you save an image with the inspector opened on both x and y, x
>> asTime and y asTime
>> > > > and provide a link to it? like that I can inspect it in all
>> detail...
>> > > >
>> > > > On 2013-06-06, at 17:51, dmacq  wrote:
>> > > >
>> > > > > I tried it again this morning and still had the problem.
>> > > > >
>> > > > > This is interesting.
>> > > > >
>> > > > > | x y |
>> > > > > x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7.
>> > > > > y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5
>> second: 7.
>> > > > > x = y  <-- True
>> > > > >
>> > > > > But
>> > > > > | x y |
>> > > > > x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7.
>> > > > > y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5
>> second: 7.
>> > > > > x asTime = y asTime <- False
>> > > > >
>> > > > >
>> > > > >
>> > > > > --
>> > > > > View this message in context:
>> http://forum.world.st/DateAndTime-asTime-tp4691870p4691988.html
>> > > > > Sent from the Pharo Smalltalk Users mailing list archive at
>> Nabble.com .
>> > > > >
>> > > >
>> > > >
>> > > >
>> > >
>> > >
>> > >
>> >
>> >
>> >
>>
>>
>>
>
>
>

Re: [Pharo-users] Changes-File & caching

[Sven Van Caekenberghe]

On 07 Jun 2013, at 19:45, Stéphane Ducasse  wrote:

> 
> On Jun 7, 2013, at 11:14 AM, Sven Van Caekenberghe  wrote:
> 
>> 
>> On 07 Jun 2013, at 11:07, Markus Fritsche  wrote:
>> 
>>> Hello Sven & List,
>>> 
>>> On 07.06.2013 10:45, Sven Van Caekenberghe wrote:
 Yes, it is an important problem (but the trigger is a change in Ubuntu 
 13.04). I am not an Ubuntu desktop user, I can only hope that those who 
 are will help.
>>> Well, I have 13.04 on a few laptops (2GB Atom netbook, 8GB i7 dual core and 
>>> 6GB AMD 4Core) with different file systems (ext4, btrfs) on them, so I have 
>>> quite a few configurations at hand to test with.
>> 
>> Great, we need more Linux Desktop users, the community it too Mac centric ;-)
> 
> +1
> I'm waiting that mac gets totally evil to switch :)

If you would switch and force a good UX, all Pharo users on Linux will thank 
you for it ;-)

>>> The RemoteString-Error during updates has been fixed; as I see the files 
>>> referenced by the download links have been replaced. The only "old" image 
>>> left I found was the one titled "Pharo 2.0 image" on 
>>> http://www.pharo-project.org/pharo-download which raises the error in 
>>> ScriptLoaderupdate>>#20605
>> 
>> We need to fix that then.
>> 
>> Thanks for the feedback.
>> 
>> Sven
>> 
>> --
>> Sven Van Caekenberghe
>> Proudly supporting Pharo
>> http://pharo.org
>> http://association.pharo.org
>> http://consortium.pharo.org
>> 
>> 
>> 
>> 
>> 
> 
> 

Re: [Pharo-users] DateAndTime>>asTime

[Stéphane Ducasse]

tx I will look at it.

Stef

On Jun 7, 2013, at 8:57 PM, José Comesaña  wrote:

> Done.
> 
> I hope I have made it correctly. If not, please tell me.
> 
> Regards
> 
> 2013/6/7 Stéphane Ducasse 
> Here it is https://pharo.fogbugz.com/default.asp?10869
> 
> Stef
> 
> 
> 
> 
> On Jun 7, 2013, at 8:17 PM, Stéphane Ducasse  
> wrote:
> 
>> 
>> 
>>> Hi again.
>>> 
>>> I have one first test for #readFrom:pattern:. What can I do now to send it, 
>>> where, to whom?.
>> 
>> I will create a bug entry for you and you create a slice with the test and 
>> the fix and you publish it in the pharo inbox.
>> 
>> Stef
>> 
>>> 
>>> Regards
>>> 
>>> 2013/6/7 Sven Van Caekenberghe 
>>> 
>>> On 07 Jun 2013, at 14:28, José Comesaña  wrote:
>>> 
>>> > Answers in red.
>>> >
>>> > Regards
>>> >
>>> > 2013/6/7 Sven Van Caekenberghe 
>>> >
>>> > On 07 Jun 2013, at 13:26, José Comesaña  wrote:
>>> >
>>> > > Thank you Sven.
>>> > >
>>> > > I had made the fixes myself, creating a new class for dates (I don't 
>>> > > need the complexity of Date just for determining if a date is past, I 
>>> > > don't need date arithmetic either). I just wanted to inform, mainly 
>>> > > because the bug seems to be still present in Pharo 3.0.
>>> > >
>>> > > Anyway, your solution does not work for the 'd/m/y' pattern, although 
>>> > > it does for 'd/m/yy'.
>>> >
>>> > Depends on what a single y means, right ?
>>> >
>>> > According  to documentation, one y means ...year, no matter how many 
>>> > digits supplied... (my own words, not litteral).  It means it will either 
>>> > accept ../../13 or ../../2013
>>> 
>>> Yes, that is how I understood it as well. My change adds 2000 only in the 
>>> case of 2 y's unless I am mistaken. But I must admin I didn't test it.
>>> 
>>> > > I could write the tests you suggest, if you think they are interesting.
>>> >
>>> > Yes, please do: with a good set of tests, we can discuss using concrete 
>>> > examples.
>>> >
>>> >
>>> > Sure I will. Will keep you informed!
>>> 
>>> Super.
>>> 
>>> > > Regards
>>> > >
>>> > > 2013/6/7 Sven Van Caekenberghe 
>>> > > Hi José,
>>> > >
>>> > > On 07 Jun 2013, at 12:02, José Comesaña  wrote:
>>> > >
>>> > > > Hello everybody.
>>> > > >
>>> > > > I would like to add a new improvement to this thread.
>>> > > >
>>> > > > I have noticed that Date class has a bug, or at least something to 
>>> > > > improve in readFrom:pattern: method. The initial comment states that 
>>> > > > "A year given using only two decimals is considered to be >2000.".
>>> > > >
>>> > > > But this seems to be incorrect: if you evaluate
>>> > > >
>>> > > > Date readFrom: '07/06/13' readStream pattern: 'd/m/y'
>>> > > >
>>> > > > you get:
>>> > > >
>>> > > >  7 June 0013 instead of  7 June 2013.
>>> > > >
>>> > > > I am working with version #20605
>>> > >
>>> > > The fix would be quite easy:
>>> > >
>>> > >   year := (inputStream next: 2) asInteger
>>> > >
>>> > > should be
>>> > >
>>> > >   year := 2000 + (inputStream next: 2) asInteger
>>> > >
>>> > > A more important problem is that there are no users of 
>>> > > #readFrom:pattern: in the system, not even unit tests. If we want to 
>>> > > keep the methods, someone should start by writing a couple of unit 
>>> > > tests.
>>> > >
>>> > > Sven
>>> > >
>>> > > > Thank you all for your great work.
>>> > > >
>>> > > > Regards.
>>> > > >
>>> > > >
>>> > > > 2013/6/6 Camillo Bruni 
>>> > > > can you save an image with the inspector opened on both x and y, x 
>>> > > > asTime and y asTime
>>> > > > and provide a link to it? like that I can inspect it in all detail...
>>> > > >
>>> > > > On 2013-06-06, at 17:51, dmacq  wrote:
>>> > > >
>>> > > > > I tried it again this morning and still had the problem.
>>> > > > >
>>> > > > > This is interesting.
>>> > > > >
>>> > > > > | x y |
>>> > > > > x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7.
>>> > > > > y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5 
>>> > > > > second: 7.
>>> > > > > x = y  <-- True
>>> > > > >
>>> > > > > But
>>> > > > > | x y |
>>> > > > > x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7.
>>> > > > > y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5 
>>> > > > > second: 7.
>>> > > > > x asTime = y asTime <- False
>>> > > > >
>>> > > > >
>>> > > > >
>>> > > > > --
>>> > > > > View this message in context: 
>>> > > > > http://forum.world.st/DateAndTime-asTime-tp4691870p4691988.html
>>> > > > > Sent from the Pharo Smalltalk Users mailing list archive at 
>>> > > > > Nabble.com.
>>> > > > >
>>> > > >
>>> > > >
>>> > > >
>>> > >
>>> > >
>>> > >
>>> >
>>> >
>>> >
>>> 
>>> 
>>> 
>> 
> 
> 

Re: [Pharo-users] DateAndTime>>asTime

[Stéphane Ducasse]

Jose

normally we do not summit code in the pane of the bug tracker, we commit a 
slice (click + slice in the monticello browser) 
in the inbox folder.

Stef

On Jun 7, 2013, at 9:12 PM, Stéphane Ducasse  wrote:

> tx I will look at it.
> 
> Stef
> 
> On Jun 7, 2013, at 8:57 PM, José Comesaña  wrote:
> 
>> Done.
>> 
>> I hope I have made it correctly. If not, please tell me.
>> 
>> Regards
>> 
>> 2013/6/7 Stéphane Ducasse 
>> Here it is https://pharo.fogbugz.com/default.asp?10869
>> 
>> Stef
>> 
>> 
>> 
>> 
>> On Jun 7, 2013, at 8:17 PM, Stéphane Ducasse  
>> wrote:
>> 
>>> 
>>> 
 Hi again.
 
 I have one first test for #readFrom:pattern:. What can I do now to send 
 it, where, to whom?.
>>> 
>>> I will create a bug entry for you and you create a slice with the test and 
>>> the fix and you publish it in the pharo inbox.
>>> 
>>> Stef
>>> 
 
 Regards
 
 2013/6/7 Sven Van Caekenberghe 
 
 On 07 Jun 2013, at 14:28, José Comesaña  wrote:
 
 > Answers in red.
 >
 > Regards
 >
 > 2013/6/7 Sven Van Caekenberghe 
 >
 > On 07 Jun 2013, at 13:26, José Comesaña  wrote:
 >
 > > Thank you Sven.
 > >
 > > I had made the fixes myself, creating a new class for dates (I don't 
 > > need the complexity of Date just for determining if a date is past, I 
 > > don't need date arithmetic either). I just wanted to inform, mainly 
 > > because the bug seems to be still present in Pharo 3.0.
 > >
 > > Anyway, your solution does not work for the 'd/m/y' pattern, although 
 > > it does for 'd/m/yy'.
 >
 > Depends on what a single y means, right ?
 >
 > According  to documentation, one y means ...year, no matter how many 
 > digits supplied... (my own words, not litteral).  It means it will 
 > either accept ../../13 or ../../2013
 
 Yes, that is how I understood it as well. My change adds 2000 only in the 
 case of 2 y's unless I am mistaken. But I must admin I didn't test it.
 
 > > I could write the tests you suggest, if you think they are interesting.
 >
 > Yes, please do: with a good set of tests, we can discuss using concrete 
 > examples.
 >
 >
 > Sure I will. Will keep you informed!
 
 Super.
 
 > > Regards
 > >
 > > 2013/6/7 Sven Van Caekenberghe 
 > > Hi José,
 > >
 > > On 07 Jun 2013, at 12:02, José Comesaña  
 > > wrote:
 > >
 > > > Hello everybody.
 > > >
 > > > I would like to add a new improvement to this thread.
 > > >
 > > > I have noticed that Date class has a bug, or at least something to 
 > > > improve in readFrom:pattern: method. The initial comment states that 
 > > > "A year given using only two decimals is considered to be >2000.".
 > > >
 > > > But this seems to be incorrect: if you evaluate
 > > >
 > > > Date readFrom: '07/06/13' readStream pattern: 'd/m/y'
 > > >
 > > > you get:
 > > >
 > > >  7 June 0013 instead of  7 June 2013.
 > > >
 > > > I am working with version #20605
 > >
 > > The fix would be quite easy:
 > >
 > >   year := (inputStream next: 2) asInteger
 > >
 > > should be
 > >
 > >   year := 2000 + (inputStream next: 2) asInteger
 > >
 > > A more important problem is that there are no users of 
 > > #readFrom:pattern: in the system, not even unit tests. If we want to 
 > > keep the methods, someone should start by writing a couple of unit 
 > > tests.
 > >
 > > Sven
 > >
 > > > Thank you all for your great work.
 > > >
 > > > Regards.
 > > >
 > > >
 > > > 2013/6/6 Camillo Bruni 
 > > > can you save an image with the inspector opened on both x and y, x 
 > > > asTime and y asTime
 > > > and provide a link to it? like that I can inspect it in all detail...
 > > >
 > > > On 2013-06-06, at 17:51, dmacq  wrote:
 > > >
 > > > > I tried it again this morning and still had the problem.
 > > > >
 > > > > This is interesting.
 > > > >
 > > > > | x y |
 > > > > x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7.
 > > > > y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5 
 > > > > second: 7.
 > > > > x = y  <-- True
 > > > >
 > > > > But
 > > > > | x y |
 > > > > x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7.
 > > > > y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5 
 > > > > second: 7.
 > > > > x asTime = y asTime <- False
 > > > >
 > > > >
 > > > >
 > > > > --
 > > > > View this message in context: 
 > > > > http://forum.world.st/DateAndTime-asTime-tp4691870p4691988.html
 > > > > Sent from the Pharo Smalltalk Users mailing list archive at 
 > > > > Nabble.com.
 > > > >
 > > >
 > > >
 > > >
 > >

Re: [Pharo-users] DateAndTime>>asTime

[José Comesaña]

Ok, I will correct it tomorrow.

Txs



El 07/06/2013, a las 21:45, Stéphane Ducasse  
escribió:

> Jose
> 
> normally we do not summit code in the pane of the bug tracker, we commit a 
> slice (click + slice in the monticello browser) 
> in the inbox folder.
> 
> Stef
> 
> On Jun 7, 2013, at 9:12 PM, Stéphane Ducasse  
> wrote:
> 
>> tx I will look at it.
>> 
>> Stef
>> 
>> On Jun 7, 2013, at 8:57 PM, José Comesaña  wrote:
>> 
>>> Done.
>>> 
>>> I hope I have made it correctly. If not, please tell me.
>>> 
>>> Regards
>>> 
>>> 2013/6/7 Stéphane Ducasse 
 Here it is https://pharo.fogbugz.com/default.asp?10869
 
 Stef
 
 
 
 
 On Jun 7, 2013, at 8:17 PM, Stéphane Ducasse  
 wrote:
 
> 
> 
>> Hi again.
>> 
>> I have one first test for #readFrom:pattern:. What can I do now to send 
>> it, where, to whom?.
> 
> I will create a bug entry for you and you create a slice with the test 
> and the fix and you publish it in the pharo inbox.
> 
> Stef
> 
>> 
>> Regards
>> 
>> 2013/6/7 Sven Van Caekenberghe 
>>> 
>>> On 07 Jun 2013, at 14:28, José Comesaña  wrote:
>>> 
>>> > Answers in red.
>>> >
>>> > Regards
>>> >
>>> > 2013/6/7 Sven Van Caekenberghe 
>>> >
>>> > On 07 Jun 2013, at 13:26, José Comesaña  
>>> > wrote:
>>> >
>>> > > Thank you Sven.
>>> > >
>>> > > I had made the fixes myself, creating a new class for dates (I 
>>> > > don't need the complexity of Date just for determining if a date is 
>>> > > past, I don't need date arithmetic either). I just wanted to 
>>> > > inform, mainly because the bug seems to be still present in Pharo 
>>> > > 3.0.
>>> > >
>>> > > Anyway, your solution does not work for the 'd/m/y' pattern, 
>>> > > although it does for 'd/m/yy'.
>>> >
>>> > Depends on what a single y means, right ?
>>> >
>>> > According  to documentation, one y means ...year, no matter how many 
>>> > digits supplied... (my own words, not litteral).  It means it will 
>>> > either accept ../../13 or ../../2013
>>> 
>>> Yes, that is how I understood it as well. My change adds 2000 only in 
>>> the case of 2 y's unless I am mistaken. But I must admin I didn't test 
>>> it.
>>> 
>>> > > I could write the tests you suggest, if you think they are 
>>> > > interesting.
>>> >
>>> > Yes, please do: with a good set of tests, we can discuss using 
>>> > concrete examples.
>>> >
>>> >
>>> > Sure I will. Will keep you informed!
>>> 
>>> Super.
>>> 
>>> > > Regards
>>> > >
>>> > > 2013/6/7 Sven Van Caekenberghe 
>>> > > Hi José,
>>> > >
>>> > > On 07 Jun 2013, at 12:02, José Comesaña  
>>> > > wrote:
>>> > >
>>> > > > Hello everybody.
>>> > > >
>>> > > > I would like to add a new improvement to this thread.
>>> > > >
>>> > > > I have noticed that Date class has a bug, or at least something 
>>> > > > to improve in readFrom:pattern: method. The initial comment 
>>> > > > states that "A year given using only two decimals is considered 
>>> > > > to be >2000.".
>>> > > >
>>> > > > But this seems to be incorrect: if you evaluate
>>> > > >
>>> > > > Date readFrom: '07/06/13' readStream pattern: 'd/m/y'
>>> > > >
>>> > > > you get:
>>> > > >
>>> > > >  7 June 0013 instead of  7 June 2013.
>>> > > >
>>> > > > I am working with version #20605
>>> > >
>>> > > The fix would be quite easy:
>>> > >
>>> > >   year := (inputStream next: 2) asInteger
>>> > >
>>> > > should be
>>> > >
>>> > >   year := 2000 + (inputStream next: 2) asInteger
>>> > >
>>> > > A more important problem is that there are no users of 
>>> > > #readFrom:pattern: in the system, not even unit tests. If we want 
>>> > > to keep the methods, someone should start by writing a couple of 
>>> > > unit tests.
>>> > >
>>> > > Sven
>>> > >
>>> > > > Thank you all for your great work.
>>> > > >
>>> > > > Regards.
>>> > > >
>>> > > >
>>> > > > 2013/6/6 Camillo Bruni 
>>> > > > can you save an image with the inspector opened on both x and y, 
>>> > > > x asTime and y asTime
>>> > > > and provide a link to it? like that I can inspect it in all 
>>> > > > detail...
>>> > > >
>>> > > > On 2013-06-06, at 17:51, dmacq  wrote:
>>> > > >
>>> > > > > I tried it again this morning and still had the problem.
>>> > > > >
>>> > > > > This is interesting.
>>> > > > >
>>> > > > > | x y |
>>> > > > > x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 
>>> > > > > 7.
>>> > > > > y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5 
>>> > > > > second: 7.
>>> > > > > x = y  <-- True
>>> > > > >
>>> > > > > But

Re: [Pharo-users] DateAndTime>>asTime

[Stéphane Ducasse]

thanks :)
This is less work for us and the process can automatically check the code and 
run the tests automatically.
Stef

On Jun 7, 2013, at 10:16 PM, José Comesaña  wrote:

> Ok, I will correct it tomorrow.
> 
> Txs
> 
> 
> 
> El 07/06/2013, a las 21:45, Stéphane Ducasse  
> escribió:
> 
>> Jose
>> 
>> normally we do not summit code in the pane of the bug tracker, we commit a 
>> slice (click + slice in the monticello browser) 
>> in the inbox folder.
>> 
>> Stef
>> 
>> On Jun 7, 2013, at 9:12 PM, Stéphane Ducasse  
>> wrote:
>> 
>>> tx I will look at it.
>>> 
>>> Stef
>>> 
>>> On Jun 7, 2013, at 8:57 PM, José Comesaña  wrote:
>>> 
 Done.
 
 I hope I have made it correctly. If not, please tell me.
 
 Regards
 
 2013/6/7 Stéphane Ducasse 
 Here it is https://pharo.fogbugz.com/default.asp?10869
 
 Stef
 
 
 
 
 On Jun 7, 2013, at 8:17 PM, Stéphane Ducasse  
 wrote:
 
> 
> 
>> Hi again.
>> 
>> I have one first test for #readFrom:pattern:. What can I do now to send 
>> it, where, to whom?.
> 
> I will create a bug entry for you and you create a slice with the test 
> and the fix and you publish it in the pharo inbox.
> 
> Stef
> 
>> 
>> Regards
>> 
>> 2013/6/7 Sven Van Caekenberghe 
>> 
>> On 07 Jun 2013, at 14:28, José Comesaña  wrote:
>> 
>> > Answers in red.
>> >
>> > Regards
>> >
>> > 2013/6/7 Sven Van Caekenberghe 
>> >
>> > On 07 Jun 2013, at 13:26, José Comesaña  
>> > wrote:
>> >
>> > > Thank you Sven.
>> > >
>> > > I had made the fixes myself, creating a new class for dates (I don't 
>> > > need the complexity of Date just for determining if a date is past, 
>> > > I don't need date arithmetic either). I just wanted to inform, 
>> > > mainly because the bug seems to be still present in Pharo 3.0.
>> > >
>> > > Anyway, your solution does not work for the 'd/m/y' pattern, 
>> > > although it does for 'd/m/yy'.
>> >
>> > Depends on what a single y means, right ?
>> >
>> > According  to documentation, one y means ...year, no matter how many 
>> > digits supplied... (my own words, not litteral).  It means it will 
>> > either accept ../../13 or ../../2013
>> 
>> Yes, that is how I understood it as well. My change adds 2000 only in 
>> the case of 2 y's unless I am mistaken. But I must admin I didn't test 
>> it.
>> 
>> > > I could write the tests you suggest, if you think they are 
>> > > interesting.
>> >
>> > Yes, please do: with a good set of tests, we can discuss using 
>> > concrete examples.
>> >
>> >
>> > Sure I will. Will keep you informed!
>> 
>> Super.
>> 
>> > > Regards
>> > >
>> > > 2013/6/7 Sven Van Caekenberghe 
>> > > Hi José,
>> > >
>> > > On 07 Jun 2013, at 12:02, José Comesaña  
>> > > wrote:
>> > >
>> > > > Hello everybody.
>> > > >
>> > > > I would like to add a new improvement to this thread.
>> > > >
>> > > > I have noticed that Date class has a bug, or at least something to 
>> > > > improve in readFrom:pattern: method. The initial comment states 
>> > > > that "A year given using only two decimals is considered to be 
>> > > > >2000.".
>> > > >
>> > > > But this seems to be incorrect: if you evaluate
>> > > >
>> > > > Date readFrom: '07/06/13' readStream pattern: 'd/m/y'
>> > > >
>> > > > you get:
>> > > >
>> > > >  7 June 0013 instead of  7 June 2013.
>> > > >
>> > > > I am working with version #20605
>> > >
>> > > The fix would be quite easy:
>> > >
>> > >   year := (inputStream next: 2) asInteger
>> > >
>> > > should be
>> > >
>> > >   year := 2000 + (inputStream next: 2) asInteger
>> > >
>> > > A more important problem is that there are no users of 
>> > > #readFrom:pattern: in the system, not even unit tests. If we want to 
>> > > keep the methods, someone should start by writing a couple of unit 
>> > > tests.
>> > >
>> > > Sven
>> > >
>> > > > Thank you all for your great work.
>> > > >
>> > > > Regards.
>> > > >
>> > > >
>> > > > 2013/6/6 Camillo Bruni 
>> > > > can you save an image with the inspector opened on both x and y, x 
>> > > > asTime and y asTime
>> > > > and provide a link to it? like that I can inspect it in all 
>> > > > detail...
>> > > >
>> > > > On 2013-06-06, at 17:51, dmacq  wrote:
>> > > >
>> > > > > I tried it again this morning and still had the problem.
>> > > > >
>> > > > > This is interesting.
>> > > > >
>> > > > > | x y |
>> > > > > x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 
>> > > > > 7.
>> > > > > y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5 
>> > > >

[Pharo-users] Blog Entry About Pharo

[Bahman Movaqar]

Hi all,

I wrote a blog entry[1] about Pharo and would appreciate your opinions
and possible corrections.

PS:  Anonymous comments are enabled on my website.  I had to disable
user creation to fight spam.  However if you'd like a user, I'll be
pleased to create one for you.

[1] http://www.bahmanm.com/blogs/a-new-platform-for-business-app-development

-- 
Bahman Movaqar  (http://BahmanM.com)
ERP Evaluation, Implementation, Deployment Consultant