Post

Replies

Boosts

Views

Activity

Comment on "illegal character encoding in string literal" warnings in Xcode
Hmmm. Works for me that way, too, pasting the char* assignment you've posted and also the identical-looking original warning-causing line with supposedly the exact original bytes. Maybe something in project settings? Thank you for your attention, Ed. (Now I'm chasing an actual crash after a random N of invoking-then-disposing a window-displaying thread that takes data from a sound capture callback. I hope to nail that tomorrow and then get back to this less critical issue.) Cheers! Dave
Jun ’25
Comment on "illegal character encoding in string literal" warnings in Xcode
char*ppstrs[9]={"user","zero","ctr","ø∆1","ø∆2","ø∆3","†∆1","†∆2","†∆3"}; The above line has the highlited warning "Illegal character encoding in string literal". These characters are all in the Mac OS Roman encoding and used to display properly. In error messages, there are a number of cases of "can't open file", and to distinguish them I've used things like "cänt", "côn't", and so on. This is not a big deal; just curious if there's an easy fix.....
Jun ’25