Re: Objective-C++ 2.0 - C++ valued properties

Subject: Re: Objective-C++ 2.0 - C++ valued properties
From: Scott Thompson <email@hidden>
Date: Sun, 16 Mar 2008 08:42:20 -0500

In a quick test, I find Test2 and Test3 compile to identical code, but Test1 does some extra busywork that doesn't seem to accomplish anything at first glance. However, all three cause setPosition: to be called with the specified Vector3D, so the problem would seem to be with your setPosition: (or the synthesized setPosition:, as the case may be).

My experience is somewhat different. In my test, case 2 and 3 do compile, and behave, as expected. In stepping through them with the debugger, they actually call setPosition. Test 1, however, results in some code that moves the three components of the Vector3D:

0x00005755 <+0441> mov -0x18(�p),�x

0x00005758 <+0444> mov �x,-0x24(�p)

0x0000575b <+0447> mov -0x14(�p),�x

0x0000575e <+0450> mov �x,-0x20(�p)

0x00005761 <+0453> mov -0x10(�p),�x

0x00005764 <+0456> mov �x,-0x1c(�p)

But there's no call to obj_msgSend and a breakpoint in setPosition is never called. :-(

Thank you for checking that on your own system. I will take your example and my own ode and use it to generate a bug report.

If you'll excuse some Danish (I'm not sure what the Swedish equivalent might be)

Mange Hilsner,

Scott

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References:
	>Objective-C++ 2.0 - C++ valued properties (From: Scott Thompson <email@hidden>)
	>Re: Objective-C++ 2.0 - C++ valued properties (From: Jens Ayton <email@hidden>)

Prev by Date: Re: Headers in Framework
Next by Date: Re: Getting line numbers in crash logs with dwarf
Previous by thread: Re: Objective-C++ 2.0 - C++ valued properties
Next by thread: Re: Objective-C++ 2.0 - C++ valued properties
Index(es):
- Date
- Thread