On Jun 21, 2005, at 4:12 AM, Frederic Stark wrote:
I am sending this to gnustep-dev crossposted to gcc. Maybe this
isn't the right mailing list. See at the end of the post for a 40
line program that exhibit the bad behavior.
Problem:
If a is a fault (ie: changes its isa pointer during
fo
Timothy J. Wood wrote:
[crunch]
The code works correctly under Mac OS X.
I just checked under linux/gcc 3.4 and the code works fine there. Maybe
this is a gcc 3.2 specific problem. I'll check gcc 3.4 windows one of
those days.
The Apple runtime doesn't have this design choice, so it can'
On Jun 21, 2005, at 1:20 PM, Frederic Stark wrote:
Timothy J. Wood wrote:
[crunch]
The code works correctly under Mac OS X.
I just checked under linux/gcc 3.4 and the code works fine there.
Maybe this is a gcc 3.2 specific problem. I'll check gcc 3.4 windows
one of those days.
It is a
Jeremy Bettis wrote:
- Original Message - From: "Frederic Stark" <[EMAIL PROTECTED]>
To: ;
Sent: Tuesday, June 21, 2005 6:12 AM
Subject: Problem implementing faults in Objective-C
: Uncaught exception NSInvalidArgumentException, reason: B(instance)
does not recognize
- Original Message -
From: "Frederic Stark" <[EMAIL PROTECTED]>
To: ;
Sent: Tuesday, June 21, 2005 6:12 AM
Subject: Problem implementing faults in Objective-C
: Uncaught exception NSInvalidArgumentException, reason: B(instance) does
not recognize method1:
Ugh nasty
Hi all,
I am sending this to gnustep-dev crossposted to gcc. Maybe this isn't
the right mailing list. See at the end of the post for a 40 line program
that exhibit the bad behavior.
Problem:
If a is a fault (ie: changes its isa pointer during forwardInvocation),
then:
[a method1:[a method2
