2020-01-23 23:30:08.598853+01 by Dan Lyke 3 comments
Today I learned that \x13 in a string constant does not display in XCode, which makes it just freakin' wonderful to debug why that NSDictionary member wasn't showing up when I JSON encoded it and sent it to JavaScript. How the \x13 got in there is also a mystery.
[ related topics: Cryptography ]
comments in ascending chronological order (reverse):
#Comment Re: Today I learned that x13 in a string made: 2020-01-24 00:29:23.853369+01 by: markd
Emacs file-save muscle memory? Happens to me all.the.time. It doesn't appear in show invisibles. ObjC generally gives inscrutable errors when one happens outside of a string. Swift at least tells me there's an illegal character in the file.
#Comment Re: Today I learned that x13 in a string made: 2020-01-24 21:17:08.187304+01 by: Dan Lyke
Probably Emacs muscle memory, 'cause I'm using Emacs to edit the JavaScript portion of this.
#Comment Re: Today I learned that x13 in a string made: 2020-01-26 12:22:09.869669+01 by: meuon
Oh the times I've looked at stuff in hex editor mode to find such crap, often in XML.
We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.
Flutterby™ is a trademark claimed by
Dan Lyke for the web publications at www.flutterby.com and www.flutterby.net.