You are correct in your discussion and I understand what you are saying.
Yes, I'm not trying to change any data the c_str() is pointing to and
yes I agree there are no guarantees as to where the data is located.
My only reason for stating my examination was in hopes of
'triggering' someone's memory as to what might be causing the things
that I'm seeing.
What are you seeing exactly? You original post doesn't make that
really clear because of the "examination" discussion.
The fact is c_str() does not work for me. I don't know why.
We don't know why either... need to see a code sample... ideally
something that we could compile to see the issue ourselves.
Since
this code (framework) compiles other platforms and CodeWarrior, I can
only assume that I'm missing something in the Xcode setup.
Not sure I would 100% agree with that assumption. Just to many factors
in the equation... it could be a simple mistake in your code that only
shows up when compiled by gcc and/or when using Mac OS X related
standard library.
-Shawn
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
