On Fri, May 8, 2009 at 9:56 AM, Drew Lawson <d...@furrfu.com> wrote: > According to Alex Curylo: > >> >> On 8-May-09, at 8:55 AM, cocoa-dev-requ...@lists.apple.com wrote: >> >> > mycppstring = std::string([[myNSTextField stringValue] UTF8String]); >> > >> > >> > But it keeps crashing. What's the recommended way? >> >> I have no idea, but it works for me to simply assign it without the >> constructor. Why, here's an example in the file I'm working on right >> now, fancy that: > > The only other gotcha I can think of (because it annoys me) is that > std::string does not play nice with null pointers. Is it possible > that stringValue returns nil? > > Hmm, I had one other thought. There are several std::string > constructors, depending on the parameter type. In ObjC++, is it > unambiguous at compile time that the expression is "const char*"?
Yes. Otherwise, it would be a compile-time error. std::string only has two single-parameter constructors, one takes a (const char*) and one takes a (const std::string&), so unless you've defined your own UTF8String method that returns a std::string, none of the other constructors will match. -- Clark S. Cox III clarkc...@gmail.com _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
