"outline" member illegal?
"outline" member illegal?
- Subject: "outline" member illegal?
- From: Dix Lorenz <email@hidden>
- Date: Sun, 4 May 2003 12:50:32 +0200
Hi,
is there any reason why I shouldn't have a member variable called
"outline"? In a datasource/delegate for an NSOutlineView I stored the
pointer to the outlineview in a member called "outline". The whole
thing worked fine, except: every message I would send to "outline"
would crash the program. The stack would hang at "obj_msg_send" (or
whatever it is called exactly) and after checking for hours if it was
set correctly (it was), if anything had been released (it hadn't) or if
anything else was wrong (it wasn't) I decided it would crash at the
call itself and in that special moment "outline" was not was it was
supposed to be. Or dynamic messaging messed around. Anyway, I changed
the name to mOutline, adjusted the nib, and after that everything went
fine.
While it is solved, any ideas why it would fail? My object's superclass
doesn't have any members or functions "outline", and that one descends
from "NSObject", which also shouldn't have. There are no global
variables of that name. Also, there were no compiler warnings ("outline
doesn't respond to 'reloadData'!) and I checked if the "outlineView" my
datasource-methods received were the same as my variable. Both of which
should have failed if there was a different "outline" around...
Dix
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.