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 <[email protected]> wrote: > > On 17 Jan 2014, at 18:43, Johan Brichau <[email protected]> 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 you, is that fine? >> > ok! > >> Johan >> >> Sent from my iPad >> >>> On 17 Jan 2014, at 13:37, Marcus Denker <[email protected]> wrote: >>> >>> 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 <[email protected]> wrote: >>>> >>>> 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 >>>> older vm (6 sep). >>>> >>>> Since it's difficult to create a separate public test for this to recreate >>>> the problem, how do we go about this? >>>> >>>> cheers, >>>> Johan >>> >>> >> > >
