Multiple ivars with the same name

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

Multiple ivars with the same name

Boris Popov, DeepCove Labs (SNN)
See attached, I've reported this quite a while ago, but never had a
chance to follow-up, so here goes.

Cheers!

-Boris

--
+1.604.689.0322
DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5

[hidden email]

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.


doubleivar.jpg (61K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Multiple ivars with the same name

Michael Lucas-Smith
I see that occasionally - and when it gets published, you then have a
major issue - it won't load, it gets a component unloadable error and
then crashes calling #comment on nil.

> See attached, I've reported this quite a while ago, but never had a
> chance to follow-up, so here goes.

> Cheers!

> -Boris


Reply | Threaded
Open this post in threaded view
|

RE: Multiple ivars with the same name

Thomas Brodt
I also had them already. And you even can't replay them in the change list because it complains about a duplicate instance variable
name in hierarchy (!). At least you can fix that more easily than a published package. Has anyone already found out how it is
produced?

Thomas

> -----Original Message-----
> From: Michael Lucas-Smith
> [mailto:[hidden email]]
> Sent: Tuesday, November 07, 2006 10:44 PM
> To: Boris Popov
> Cc: vwnc-list
> Subject: Re: Multiple ivars with the same name
>
> I see that occasionally - and when it gets published, you then have a
> major issue - it won't load, it gets a component unloadable error and
> then crashes calling #comment on nil.
>
> > See attached, I've reported this quite a while ago, but never had a
> > chance to follow-up, so here goes.
>
> > Cheers!
>
> > -Boris
>
>
>

Reply | Threaded
Open this post in threaded view
|

AW: Multiple ivars with the same name

Nowak, Helge
if you want (should anyone want to?) you simply *can* do it, in one class or in a class hierarchy. The system will warn you twice that the ivar is overloaded you can say "continue" and you are done. Ways to do it accidentally I didn't explore.

Cheers
Helge

-----Ursprüngliche Nachricht-----
Von: Thomas Brodt [mailto:[hidden email]]
Gesendet: Mittwoch, 8. November 2006 09:50
An: 'vwnc-list'
Betreff: RE: Multiple ivars with the same name


I also had them already. And you even can't replay them in the change list because it complains about a duplicate instance variable
name in hierarchy (!). At least you can fix that more easily than a published package. Has anyone already found out how it is
produced?

Thomas

> -----Original Message-----
> From: Michael Lucas-Smith
> [mailto:[hidden email]]
> Sent: Tuesday, November 07, 2006 10:44 PM
> To: Boris Popov
> Cc: vwnc-list
> Subject: Re: Multiple ivars with the same name
>
> I see that occasionally - and when it gets published, you then have a
> major issue - it won't load, it gets a component unloadable error and
> then crashes calling #comment on nil.
>
> > See attached, I've reported this quite a while ago, but never had a
> > chance to follow-up, so here goes.
>
> > Cheers!
>
> > -Boris
>
>
>

Reply | Threaded
Open this post in threaded view
|

RE: Multiple ivars with the same name

Thomas Brodt
Actually I was looking for the way to *accidentally* produce this mess, as I - as a brave and reasonable developer - would never
produce this intentionally :)

I vaguely remember that it happened using the tools that modify the class definition, e.g. UIPainter/UIDefiner, LensDataModeller or
alike, but unfortunately, it is too vague. (And no, there was no warning popping up that variables were overloaded.)

Thomas

> -----Original Message-----
> From: Nowak, Helge [mailto:[hidden email]]
> Sent: Wednesday, November 08, 2006 11:33 AM
> To: Thomas Brodt; vwnc-list
> Subject: AW: Multiple ivars with the same name
>
> if you want (should anyone want to?) you simply *can* do it,
> in one class or in a class hierarchy. The system will warn
> you twice that the ivar is overloaded you can say "continue"
> and you are done. Ways to do it accidentally I didn't explore.
>
> Cheers
> Helge
>
> -----Ursprüngliche Nachricht-----
> Von: Thomas Brodt [mailto:[hidden email]]
> Gesendet: Mittwoch, 8. November 2006 09:50
> An: 'vwnc-list'
> Betreff: RE: Multiple ivars with the same name
>
>
> I also had them already. And you even can't replay them in
> the change list because it complains about a duplicate
> instance variable
> name in hierarchy (!). At least you can fix that more easily
> than a published package. Has anyone already found out how it is
> produced?
>
> Thomas
>
> > -----Original Message-----
> > From: Michael Lucas-Smith
> > [mailto:[hidden email]]
> > Sent: Tuesday, November 07, 2006 10:44 PM
> > To: Boris Popov
> > Cc: vwnc-list
> > Subject: Re: Multiple ivars with the same name
> >
> > I see that occasionally - and when it gets published, you
> then have a
> > major issue - it won't load, it gets a component unloadable
> error and
> > then crashes calling #comment on nil.
> >
> > > See attached, I've reported this quite a while ago, but
> never had a
> > > chance to follow-up, so here goes.
> >
> > > Cheers!
> >
> > > -Boris
> >
> >
> >
>
>

Reply | Threaded
Open this post in threaded view
|

AW: Multiple ivars with the same name

Nowak, Helge
you are right. Assuming everybody on the list to be a brave and reasonable developer what I actually wanted to say: is there a reason at all that the system doesn't prohibit it completely? Just being really curious.

Cheers
Helge

-----Ursprüngliche Nachricht-----
Von: Thomas Brodt [mailto:[hidden email]]
Gesendet: Mittwoch, 8. November 2006 12:08
An: Nowak, Helge; 'vwnc-list'
Betreff: RE: Multiple ivars with the same name


Actually I was looking for the way to *accidentally* produce this mess, as I - as a brave and reasonable developer - would never
produce this intentionally :)

I vaguely remember that it happened using the tools that modify the class definition, e.g. UIPainter/UIDefiner, LensDataModeller or
alike, but unfortunately, it is too vague. (And no, there was no warning popping up that variables were overloaded.)

Thomas

> -----Original Message-----
> From: Nowak, Helge [mailto:[hidden email]]
> Sent: Wednesday, November 08, 2006 11:33 AM
> To: Thomas Brodt; vwnc-list
> Subject: AW: Multiple ivars with the same name
>
> if you want (should anyone want to?) you simply *can* do it,
> in one class or in a class hierarchy. The system will warn
> you twice that the ivar is overloaded you can say "continue"
> and you are done. Ways to do it accidentally I didn't explore.
>
> Cheers
> Helge
>
> -----Ursprüngliche Nachricht-----
> Von: Thomas Brodt [mailto:[hidden email]]
> Gesendet: Mittwoch, 8. November 2006 09:50
> An: 'vwnc-list'
> Betreff: RE: Multiple ivars with the same name
>
>
> I also had them already. And you even can't replay them in
> the change list because it complains about a duplicate
> instance variable
> name in hierarchy (!). At least you can fix that more easily
> than a published package. Has anyone already found out how it is
> produced?
>
> Thomas
>
> > -----Original Message-----
> > From: Michael Lucas-Smith
> > [mailto:[hidden email]]
> > Sent: Tuesday, November 07, 2006 10:44 PM
> > To: Boris Popov
> > Cc: vwnc-list
> > Subject: Re: Multiple ivars with the same name
> >
> > I see that occasionally - and when it gets published, you
> then have a
> > major issue - it won't load, it gets a component unloadable
> error and
> > then crashes calling #comment on nil.
> >
> > > See attached, I've reported this quite a while ago, but
> never had a
> > > chance to follow-up, so here goes.
> >
> > > Cheers!
> >
> > > -Boris
> >
> >
> >
>
>

Reply | Threaded
Open this post in threaded view
|

Re: Multiple ivars with the same name

Randy Coulman
In reply to this post by Thomas Brodt


On 11/8/06, Thomas Brodt <[hidden email]> wrote:
I also had them already. And you even can't replay them in the change list because it complains about a duplicate instance variable
name in hierarchy (!). At least you can fix that more easily than a published package. Has anyone already found out how it is
produced?

The last time I had this problem, I'm pretty sure (but not positive) it came when I was recovering an image by replaying changes from the change list.  I don't recall seeing any kind of warning in this case.

Randy
--
Randy Coulman
[hidden email]
Reply | Threaded
Open this post in threaded view
|

AW: Multiple ivars with the same name

Mülheims, Klaus
In reply to this post by Boris Popov, DeepCove Labs (SNN)
Hi,
 
iI had this problem a few days ago too. And if I remember correctly, the reason was, that I replayed my changes, because my image crashed.
Probably, it happens if the change list contains the adding of an ivar, which is then done twice. VisualWorks doesn't seem to have a problem whith it (why not?), but Store has.
 
Greetings
 
Klaus
 
Collogia AG
Ubierring 11
 
50678 Köln
Germany
+49 221 336080
http://www.collogia.de
 


Von: Randy Coulman [mailto:[hidden email]]
Gesendet: Mittwoch, 8. November 2006 15:41
An: vwnc-list
Betreff: Re: Multiple ivars with the same name



On 11/8/06, Thomas Brodt <[hidden email]> wrote:
I also had them already. And you even can't replay them in the change list because it complains about a duplicate instance variable
name in hierarchy (!). At least you can fix that more easily than a published package. Has anyone already found out how it is
produced?

The last time I had this problem, I'm pretty sure (but not positive) it came when I was recovering an image by replaying changes from the change list.  I don't recall seeing any kind of warning in this case.

Randy
--
Randy Coulman
[hidden email]


Diese Nachricht ist vertraulich. Wenn Sie nicht der beabsichtigte Empfänger sind, informieren Sie bitte den Absender. Das unbefugte Kopieren oder Weiterleiten ist nicht gestattet. Wegen der Manipulierbarkeit von E-Mails übernehmen wir keine Haftung für den Inhalt.