const StringPtr != ConstStringPtr
const StringPtr != ConstStringPtr
- Subject: const StringPtr != ConstStringPtr
- From: Steve Mills <email@hidden>
- Date: Tue, 10 Jan 2006 12:30:17 -0600
During the conversion of our projects from CW to Xcode, I got errors
on all calls that passed a constant string to functions that take a
const StringPtr. If ConstStringPtr is a typedef of const unsigned
char* and StringPtr is a typedef of unsigned char*, then why does
Xcode (or gcc rather) think they're different?
void Func(const StringPtr s);
Func("\pblah"); <--error
Steve Mills
Drummer, Mac geek
http://sjmills5.home.mchsi.com/
_______________________________________________
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