Smalltalk › Pharo › Pharo Smalltalk Developers

problem with become:?

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

8 messages Options

Tudor Girba-2

problem with become:?

Hi,

If I execute the following code in the latest Pharo image:

Object subclass: #A
instanceVariableNames: ''
classVariableNames: ''
package: 'AA'.
Object subclass: #B
instanceVariableNames: ''
classVariableNames: ''
package: 'AA'.
a := A new.
b := B new.
a become: b.
a class

==> “A".

In a pre-Spur image, I used to get “B”. Is this a bug, or is there a change I am not aware of?

Cheers,
Doru

--
www.tudorgirba.com
www.feenk.com

"Things happen when they happen,
not when you talk about them happening."

Eliot Miranda-2

Re: problem with become:?

Hi Doru,

On Fri, Jan 8, 2016 at 12:02 PM, Tudor Girba <[hidden email]> wrote:

Hi,

If I execute the following code in the latest Pharo image:

Object subclass: #A
instanceVariableNames: ''
classVariableNames: ''
package: 'AA'.
Object subclass: #B
instanceVariableNames: ''
classVariableNames: ''
package: 'AA'.
a := A new.
b := B new.
a become: b.
a class

==> “A".

In a pre-Spur image, I used to get “B”. Is this a bug, or is there a change I am not aware of?

Cheers,
Doru

Looks like a bug to me. I'll fix it asap.

--
www.tudorgirba.com
www.feenk.com

"Things happen when they happen,
not when you talk about them happening."

_,,,^..^,,,_

best, Eliot

Nicolai Hess-3-2

Re: [squeak-dev] Re: problem with become:?

2016-01-08 23:09 GMT+01:00 Eliot Miranda <[hidden email]>:

Hi Doru,

On Fri, Jan 8, 2016 at 12:02 PM, Tudor Girba <[hidden email]> wrote:
Hi,

If I execute the following code in the latest Pharo image:

Object subclass: #A
instanceVariableNames: ''
classVariableNames: ''
package: 'AA'.
Object subclass: #B
instanceVariableNames: ''
classVariableNames: ''
package: 'AA'.
a := A new.
b := B new.
a become: b.
a class

==> “A".

In a pre-Spur image, I used to get “B”. Is this a bug, or is there a change I am not aware of?

Cheers,
Doru

Looks like a bug to me. I'll fix it asap.

There is another bug report at
http://bugs.squeak.org/view.php?id=7845

| obj1 obj2 |
obj1 := 'string'.
obj2 := 1.234.
obj1 become: obj2.
{obj1. obj2} "=> #('X9LÈv¾' 'string'). it should be #(1.234 'string') "

Squeak Cog Supr Virtual Machine 4.0.3427.0

Is it related?

--
www.tudorgirba.com
www.feenk.com

"Things happen when they happen,
not when you talk about them happening."

--
_,,,^..^,,,_
best, Eliot

Tudor Girba-2

Re: [Vm-dev] problem with become:?

In reply to this post by Eliot Miranda-2

Hi,

> On Jan 9, 2016, at 12:09 AM, Eliot Miranda <[hidden email]> wrote:
>
> Hi Doru,
>
> On Fri, Jan 8, 2016 at 12:02 PM, Tudor Girba <[hidden email]> wrote:
> Hi,
>
> If I execute the following code in the latest Pharo image:
>
> Object subclass: #A
> instanceVariableNames: ''
> classVariableNames: ''
> package: 'AA'.
> Object subclass: #B
> instanceVariableNames: ''
> classVariableNames: ''
> package: 'AA'.
> a := A new.
> b := B new.
> a become: b.
> a class
>
> ==> “A".
>
> In a pre-Spur image, I used to get “B”. Is this a bug, or is there a change I am not aware of?
>
> Cheers,
> Doru
>
> Looks like a bug to me. I'll fix it asap.

Thanks!

Doru

>
>
> --
> www.tudorgirba.com
> www.feenk.com
>
> "Things happen when they happen,
> not when you talk about them happening."
>
>
>
>
>
> --
> _,,,^..^,,,_
> best, Eliot

--
www.tudorgirba.com
www.feenk.com

"In a world where everything is moving ever faster,
one might have better chances to win by moving slower."

Eliot Miranda-2

Re: [Vm-dev] Re: [squeak-dev] Re: problem with become:?

In reply to this post by Nicolai Hess-3-2

On Fri, Jan 8, 2016 at 2:11 PM, Nicolai Hess <[hidden email]> wrote:

2016-01-08 23:09 GMT+01:00 Eliot Miranda <[hidden email]>:
Hi Doru,

On Fri, Jan 8, 2016 at 12:02 PM, Tudor Girba <[hidden email]> wrote:
Hi,

If I execute the following code in the latest Pharo image:

Object subclass: #A
instanceVariableNames: ''
classVariableNames: ''
package: 'AA'.
Object subclass: #B
instanceVariableNames: ''
classVariableNames: ''
package: 'AA'.
a := A new.
b := B new.
a become: b.
a class

==> “A".

In a pre-Spur image, I used to get “B”. Is this a bug, or is there a change I am not aware of?

Cheers,
Doru

Looks like a bug to me. I'll fix it asap.

There is another bug report at
http://bugs.squeak.org/view.php?id=7845

| obj1 obj2 |
obj1 := 'string'.
obj2 := 1.234.
obj1 become: obj2.
{obj1. obj2} "=> #('X9 LÈv¾' 'string'). it should be #(1.234 'string') "

Squeak Cog Supr Virtual Machine 4.0.3427.0

Is it related?

Thank you, certainly looks like it.

--
www.tudorgirba.com
www.feenk.com

"Things happen when they happen,
not when you talk about them happening."

--
_,,,^..^,,,_
best, Eliot

_,,,^..^,,,_

best, Eliot

Eliot Miranda-2

Re: [Vm-dev] Re: [squeak-dev] Re: problem with become:?

Hi Doru, Hi Nicolai,

On Fri, Jan 8, 2016 at 2:33 PM, Eliot Miranda <[hidden email]> wrote:

On Fri, Jan 8, 2016 at 2:11 PM, Nicolai Hess <[hidden email]> wrote:

2016-01-08 23:09 GMT+01:00 Eliot Miranda <[hidden email]>:
Hi Doru,

On Fri, Jan 8, 2016 at 12:02 PM, Tudor Girba <[hidden email]> wrote:
Hi,

If I execute the following code in the latest Pharo image:

Object subclass: #A
instanceVariableNames: ''
classVariableNames: ''
package: 'AA'.
Object subclass: #B
instanceVariableNames: ''
classVariableNames: ''
package: 'AA'.
a := A new.
b := B new.
a become: b.
a class

==> “A".

In a pre-Spur image, I used to get “B”. Is this a bug, or is there a change I am not aware of?

Cheers,
Doru

Looks like a bug to me. I'll fix it asap.

There is another bug report at
http://bugs.squeak.org/view.php?id=7845

| obj1 obj2 |
obj1 := 'string'.
obj2 := 1.234.
obj1 become: obj2.
{obj1. obj2} "=> #('X9 LÈv¾' 'string'). it should be #(1.234 'string') "

Squeak Cog Supr Virtual Machine 4.0.3427.0

Is it related?

Thank you, certainly looks like it.

The good news is that these are not bugs in the simulator. So I need to generate new sources and working VMs (and Esteban will need to rebuild the Pharo 5 VM) and then the bugs should be fixed. There's a slim possibility that this could be due to a Slang bug but I doubt it.

--
www.tudorgirba.com
www.feenk.com

"Things happen when they happen,
not when you talk about them happening."

_,,,^..^,,,_
best, Eliot

_,,,^..^,,,_
best, Eliot

_,,,^..^,,,_

best, Eliot

Eliot Miranda-2

Re: [Vm-dev] Re: [squeak-dev] Re: problem with become:?

Hi Doru, Hi Nicolai,

On Fri, Jan 8, 2016 at 4:20 PM, Eliot Miranda <[hidden email]> wrote:

Hi Doru, Hi Nicolai,

On Fri, Jan 8, 2016 at 2:33 PM, Eliot Miranda <[hidden email]> wrote:

On Fri, Jan 8, 2016 at 2:11 PM, Nicolai Hess <[hidden email]> wrote:

2016-01-08 23:09 GMT+01:00 Eliot Miranda <[hidden email]>:
Hi Doru,

On Fri, Jan 8, 2016 at 12:02 PM, Tudor Girba <[hidden email]> wrote:
Hi,

If I execute the following code in the latest Pharo image:

Object subclass: #A
instanceVariableNames: ''
classVariableNames: ''
package: 'AA'.
Object subclass: #B
instanceVariableNames: ''
classVariableNames: ''
package: 'AA'.
a := A new.
b := B new.
a become: b.
a class

==> “A".

In a pre-Spur image, I used to get “B”. Is this a bug, or is there a change I am not aware of?

Cheers,
Doru

Looks like a bug to me. I'll fix it asap.

There is another bug report at
http://bugs.squeak.org/view.php?id=7845

| obj1 obj2 |
obj1 := 'string'.
obj2 := 1.234.
obj1 become: obj2.
{obj1. obj2} "=> #('X9 LÈv¾' 'string'). it should be #(1.234 'string') "

Squeak Cog Supr Virtual Machine 4.0.3427.0

Is it related?

Thank you, certainly looks like it.

The good news is that these are not bugs in the simulator. So I need to generate new sources and working VMs (and Esteban will need to rebuild the Pharo 5 VM) and then the bugs should be fixed. There's a slim possibility that this could be due to a Slang bug but I doubt it.

Shows why I know. It is indeed a Slang bug, and one that shows itself only under optimisation above -O1, i.e. neither the debug nor assert VMs show the bug :-(. Alas these are the kind of bugs that take a while to track down. I'm on it though.

--
www.tudorgirba.com
www.feenk.com

"Things happen when they happen,
not when you talk about them happening."

_,,,^..^,,,_
best, Eliot

_,,,^..^,,,_
best, Eliot

_,,,^..^,,,_
best, Eliot

_,,,^..^,,,_

best, Eliot

EstebanLM

Re: [Vm-dev] Re: [squeak-dev] Re: problem with become:?

In reply to this post by Eliot Miranda-2

On 09 Jan 2016, at 01:20, Eliot Miranda <[hidden email]> wrote:

Hi Doru, Hi Nicolai,

On Fri, Jan 8, 2016 at 2:33 PM, Eliot Miranda <[hidden email]> wrote:

On Fri, Jan 8, 2016 at 2:11 PM, Nicolai Hess <[hidden email]> wrote:

2016-01-08 23:09 GMT+01:00 Eliot Miranda <[hidden email]>:
Hi Doru,

On Fri, Jan 8, 2016 at 12:02 PM, Tudor Girba <[hidden email]> wrote:
Hi,

If I execute the following code in the latest Pharo image:

Object subclass: #A
  instanceVariableNames: ''
  classVariableNames: ''
  package: 'AA'.
Object subclass: #B
  instanceVariableNames: ''
  classVariableNames: ''
  package: 'AA'.
a := A new.
b := B new.
a become: b.
a class

==> “A".

In a pre-Spur image, I used to get “B”. Is this a bug, or is there a change I am not aware of?

Cheers,
Doru

Looks like a bug to me. I'll fix it asap.

There is another bug report at
http://bugs.squeak.org/view.php?id=7845

| obj1 obj2 |
obj1 := 'string'.
obj2 := 1.234.
obj1 become: obj2.
{obj1. obj2} "=> #('X9 LÈv¾' 'string'). it should be #(1.234 'string') "

Squeak Cog Supr Virtual Machine 4.0.3427.0

Is it related?

Thank you, certainly looks like it.

The good news is that these are not bugs in the simulator. So I need to generate new sources and working VMs (and Esteban will need to rebuild the Pharo 5 VM) and then the bugs should be fixed. There's a slim possibility that this could be due to a Slang bug but I doubt it.

yes, I’m now one month behind but that’s because of a bug in pharo who is not fixed, so next week I will resume the jobs.

If there are not “issues” like this, normally VM is available immediately after a VMMaker commit :)

Esteban

--
www.tudorgirba.com
www.feenk.com

"Things happen when they happen,
not when you talk about them happening."

_,,,^..^,,,_
best, Eliot

_,,,^..^,,,_
best, Eliot

_,,,^..^,,,_
best, Eliot