Smalltalk › Cincom › VisualWorks

[7.7] Load hangs when package defines wrong subclass

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

3 messages Options

Boris Popov, DeepCove Labs (SNN)

[7.7] Load hangs when package defines wrong subclass

Loading package/parcel that defines class A as subclass of B into image where B is already subclass of A causes load to hang,

1. Start clean visual.im

2. Load attached PackageA (defines BasicForm subclass of Object; defines Form subclass of BasicForm)

3. Load attached PackageB (defines BasicForm subclass of Form)

4. At this point you can only Ctrl-Y into the loop

I believe the system is trying to report this error condition in,

self buildError: ((#errSubclassItself << #dialogs >> 'The behavior <1s> is being made a subclass of itself.') expandMacrosWith: self fullName)

but never quite manages to get itself out of the loop.

Yes, this is a real-life scenario I ran into today, so no cries of "this'll never happen" please ;)

Regards,

-Boris

DeepCove Labs Ltd.

+1 (604) 689-0322

4th floor, 595 Howe Street

Vancouver, British Columbia

Canada V6C 2T5

http://tinyurl.com/r7uw4

PacNet Services (Europe) Ltd.

+353 (0)61 714-360

Shannon Airport House, SFZ

County Clare, Ireland

http://tinyurl.com/y952amr

CONFIDENTIALITY NOTICE

This email is intended only for the persons named in the message header. Unless otherwise indicated, it contains information that is private and confidential. If you have received it in error, please notify the sender and delete the entire message including any attachments.

Thank you.

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

packages.zip (3K) Download Attachment

Samuel S. Shuster-2

Re: [7.7] Load hangs when package defines wrong subclass

Boris:

> 1. Start clean visual.im
> 2. Load attached PackageA (defines BasicForm subclass of Object; defines Form subclass of BasicForm)
> 3. Load attached PackageB (defines BasicForm subclass of Form)
> 4. At this point you can only Ctrl-Y into the loop
>
> I believe the system is trying to report this error condition in,
>
> self buildError: ((#errSubclassItself << #dialogs >> 'The behavior <1s> is being made a subclass of itself.') expandMacrosWith: self fullName)
>
> but never quite manages to get itself out of the loop.
>
> Yes, this is a real-life scenario I ran into today, so no cries of "this'll never happen" please ;)

I'm sure it can happen, but what it should do when it does is not go into endless looping (my guess is that #fullName is a problem when this happens), and cleanly raise the error. I'll create an AR for that.

You don't expect the thing to actually load of course... Right? RIGHT!!!??? :)

And So It Goes
Sames
______________________________________________________________________

Samuel S. Shuster [|]
VisualWorks Engineering, Store Project
Smalltalk Enables Success -- What Are YOU Using?

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Boris Popov, DeepCove Labs (SNN)

Re: [7.7] Load hangs when package defines wrong subclass

In reply to this post by Boris Popov, DeepCove Labs (SNN)

Re: [vwnc] [7.7] Load hangs when package defines wrong subclass

Haha, no, simple error explaining the condition would be enough.

-Boris (via BlackBerry)

----- Original Message -----
From: Samuel S. Shuster <[hidden email]>
To: Boris Popov, DeepCove Labs (YVR)
Cc: [hidden email] <[hidden email]>
Sent: Sat Feb 13 15:04:52 2010
Subject: Re: [vwnc] [7.7] Load hangs when package defines wrong subclass

Boris:

> 1. Start clean visual.im
> 2. Load attached PackageA (defines BasicForm subclass of Object; defines Form subclass of BasicForm)
> 3. Load attached PackageB (defines BasicForm subclass of Form)
> 4. At this point you can only Ctrl-Y into the loop
>
> I believe the system is trying to report this error condition in,
>
> self buildError: ((#errSubclassItself << #dialogs >> 'The behavior <1s> is being made a subclass of itself.') expandMacrosWith: self fullName)
>
> but never quite manages to get itself out of the loop.
>
> Yes, this is a real-life scenario I ran into today, so no cries of "this'll never happen" please ;)

I'm sure it can happen, but what it should do when it does is not go into endless looping (my guess is that #fullName is a problem when this happens), and cleanly raise the error. I'll create an AR for that.

You don't expect the thing to actually load of course... Right? RIGHT!!!??? :)

And So It Goes
Sames
______________________________________________________________________

Samuel S. Shuster [|]
VisualWorks Engineering, Store Project
Smalltalk Enables Success -- What Are YOU Using?

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc