Dan Thanks for the source link. I doubt I will find the time to do much for a month as I'm off to a US conference (Social Media Marketing World in San Diego) with a killer schedule before but am very interested. My first product release is just Swift/SpriteKit in iMessage so I can defer getting the packet format solid and just use Codable.
I have a long background in this kind of stuff, mostly in C++, with my old OOFILE framework providing high speed mapping direct to the ISAM data store buffers. (I still remember fun times with the SparcStation users running into offset-based crashes.) I've done a lot of code generation work in the past, using languages ranging from a weird TCL variant to Ruby and XSLT. My Realm experience may also help - I spent nearly two years on the C# team, with our SDK mapping to the C++ core. We used Fody, an IL-generator, to do compile-time reflection of RealmObject subclasses and generate schema and inject mapping calls. One strategy for the Swift parsing side I'm musing is using Codable itself and writing the generator as a custom encoder. Mike Ash wrote an [article about his binary encoder](https://www.mikeash.com/pyblog/friday-qa-2017-07-28-a-binary-coder-for-swift.html) which is on my list to play with too. On Monday, 12 February 2018 08:18:42 UTC+8, Dan Appel wrote: > > Andy, there's nothing production ready available AFAIK, but if you're > willing to take on the weight of implementing it yourself there's a bunch > of people willing to help! > >> >> -- You received this message because you are subscribed to the Google Groups "Cap'n Proto" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/capnproto.
