Re: [Pharo-dev] 1.0 largeIdentityHash fails on 64-bit Linux

Hi Ben, On Sat, Jan 6, 2018 at 8:47 PM, Ben Coman wrote: > With Linux 64 bit image > TestRunner running FLBinaryFileStreamSerializationTest > produces error "PrimitiveFailed: primitive #basicIdentityHash in > SmallFloat64 failed" > I suspect the SmallFloat64

[Pharo-dev] 1.0 largeIdentityHash fails on 64-bit Linux

With Linux 64 bit image TestRunner running FLBinaryFileStreamSerializationTest produces error "PrimitiveFailed: primitive #basicIdentityHash in SmallFloat64 failed" The same error occurs evaluating... 1.0 largeIdentityHash which works fine on 32-bit.

Re: [Pharo-dev] failing tests in Pharo 7

On 7 January 2018 at 03:08, Alistair Grant wrote: > Hi Ben, > > On 6 January 2018 at 12:09, Ben Coman wrote: > > It great having a CI system to check all our tests a passing, > > but I thought I'd go old school and run them from the TestRunner GUI >

Re: [Pharo-dev] failing tests in Pharo 7

> On 6 Jan 2018, at 20:08, Alistair Grant wrote: > > Hi Ben, > > On 6 January 2018 at 12:09, Ben Coman wrote: >> It great having a CI system to check all our tests a passing, >> but I thought I'd go old school and run them from the TestRunner GUI

Re: [Pharo-dev] (Morph>>#asDraggableMorph) isPrimitive

On Sat, Jan 6, 2018 at 8:07 PM, Eliot Miranda wrote: > Hi Denis, Hi Norbert, > > On Sat, Jan 6, 2018 at 6:30 AM, Denis Kudriashov > wrote: > >> Hi. >> >> I guess "quick" methods are compiled as special primitives. For example >> accessors are

Re: [Pharo-dev] failing tests in Pharo 7

Hi Ben, On 6 January 2018 at 12:09, Ben Coman wrote: > It great having a CI system to check all our tests a passing, > but I thought I'd go old school and run them from the TestRunner GUI > and found in a fresh latest Pharo 7 there are "128 failures, 63 errors" > > This one

Re: [Pharo-dev] (Morph>>#asDraggableMorph) isPrimitive

Hi. I guess "quick" methods are compiled as special primitives. For example accessors are primitives too: (Point >> #x) isPrimitive There is another method #isRealPrimitive which checks for explicit primitive call. 2018-01-06 13:24 GMT+01:00 Norbert Hartl : > Can anyone

Re: [Pharo-dev] Calling primitiveFailed

Hi Norbert, Not really. First we distinguish two cases: - essential primitives : provides features that cannot be implemented in Smalltalk (SmallInteger>>#+ for instance, requires to use the cpu addition) - optimisation primitives : optional, they just improve performance Optimisation

[Pharo-dev] Calling primitiveFailed

Looking through primitive methods I can see two cases. Most methods seem to call self primitiveFailed at the end of the method. But some as Object>>#at:put: do not. Can I assume that all primitive methods should call primitiveFailed at the end? Norbert

Re: [Pharo-dev] (Morph>>#asDraggableMorph) isPrimitive

Forgot the details. I downloaded image and vm with wget -O- get.pharo.org/70+vm | bash one hour ago. Norbert > Am 06.01.2018 um 13:24 schrieb Norbert Hartl : > > Can anyone explain why > > (Morph>>#asDraggableMorph) isPrimitive. > > returns true? > > Norbert

[Pharo-dev] (Morph>>#asDraggableMorph) isPrimitive

Can anyone explain why (Morph>>#asDraggableMorph) isPrimitive. returns true? Norbert

Re: [Pharo-dev] failing tests in Pharo 7

On 6 January 2018 at 19:09, Ben Coman wrote: > It great having a CI system to check all our tests a passing, > but I thought I'd go old school and run them from the TestRunner GUI > and found in a fresh latest Pharo 7 there are "128 failures, 63 errors" > So that was

Re: [Pharo-dev] New Year Wishlist (2018) ?

On 24 December 2017 at 00:58, Esteban Lorenzano wrote: > Hi everybody, > > This looks like a good moment of the year to ask all of you what would you > want to see in Pharo next year. > Features, improvements, radical changes, etc…. whatever you want. > > Of course, this

[Pharo-dev] failing tests in Pharo 7

It great having a CI system to check all our tests a passing, but I thought I'd go old school and run them from the TestRunner GUI and found in a fresh latest Pharo 7 there are "128 failures, 63 errors" This one is interesting... ArrayTest>>test0FixtureAsSetForIdentityMultiplinessTest | anElement

Re: [Pharo-dev] Iceberg merged pull requests?

Hi Esteban, Thanks for your answer. See more questions below. > Am 04.01.2018 um 09:16 schrieb Esteban Lorenzano : > >> On 3 Jan 2018, at 23:09, Stephane Ducasse wrote: >> >> You should double click on the pharo lines and looks in the update >>