Hi there,
In the process of porting our work to Pharo3, I encounter a bug where the
execution in the debugger works correctly but not outside of it.
It consistently occurs in a testcase of our code, across different images
running Pharo 30700 and latest stable vm om mac (26 dec) as well as an
This could be a compiler bug… I check that with you offline of the list (and
sign any NDA needed ;-)
Marcus
On 17 Jan 2014, at 13:27, Johan Brichau jo...@inceptive.be wrote:
Hi there,
In the process of porting our work to Pharo3, I encounter a bug where the
execution in the
When I encounter this, it’s usually in Morphic where other rendering loops
happened between the debugger and the execution :)
In a nutshell could be some thread issue :)
Ben
On 17 Jan 2014, at 09:37, Marcus Denker marcus.den...@inria.fr wrote:
This could be a compiler bug… I check that with
Hi Marcus,
I was hoping for that ;-)
An NDA will not be necessary, just that I don't need to send our code to the
list and your guarantee to eat the image afterwards ;-)
Will put it on a shared Dropbox link and email you, is that fine?
Johan
Sent from my iPad
On 17 Jan 2014, at 13:37,
On 17 Jan 2014, at 18:43, Johan Brichau jo...@inceptive.be wrote:
Hi Marcus,
I was hoping for that ;-)
An NDA will not be necessary, just that I don't need to send our code to the
list and your guarantee to eat the image afterwards ;-)
Will put it on a shared Dropbox link and email
I figured it out and it's because of this:
DateAndTime now = DateAndTime now
is true in Pharo 3
is false in Pharo 2.0
is false in Pharo 1.4
Did Pharo3 become so fast or did the clock precision decrease?
Johan
On 17 Jan 2014, at 22:23, Marcus Denker marcus.den...@inria.fr wrote:
On 17 Jan
And I will answer my own question, having found the thread on the subject [1].
short answer: DateAndTime now got faster ;-)
Good job guys! Our test was flawed because it relied (unknowingly) on the delay
in DateAndTime creation.
thx!
Johan
[1]
