<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><a href="https://github.com/apple/swift-corelibs-foundation/pull/1237#issuecomment-335767604">https://github.com/apple/swift-corelibs-foundation/pull/1237</a><div><br></div><div>May/may not be useful - unfortunately couldn’t get it working on Linux so had to close.<br><div><br><div id="AppleMailSignature">Sent from my iPhone</div><div><br>On 16 Nov 2017, at 21:18, Kevin Lundberg via swift-corelibs-dev <<a href="mailto:swift-corelibs-dev@swift.org">swift-corelibs-dev@swift.org</a>> wrote:<br><br></div><blockquote type="cite"><div><span>Thank you! I found this shortly before your message, and I’m working on that right now in my project (and it is definitely not a simple copy paste but so far it seems manageable).</span><br><span>--</span><br><span>Kevin Lundberg</span><br><span></span><br><span></span><br><span></span><br><blockquote type="cite"><span>On Nov 16, 2017, at 4:12 PM, Ian Partridge <<a href="mailto:ian@poncho.org.uk">ian@poncho.org.uk</a>> wrote:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Hi Kevin,</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>It's unintentional, in the sense that noone has done the work yet to</span><br></blockquote><blockquote type="cite"><span>implement the PropertyListDecoder in corelibs-foundation.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>However, the Darwin implementation is actually open source - see</span><br></blockquote><blockquote type="cite"><span><a href="https://github.com/apple/swift/blob/master/stdlib/public/SDK/Foundation/PlistEncoder.swift">https://github.com/apple/swift/blob/master/stdlib/public/SDK/Foundation/PlistEncoder.swift</a></span><br></blockquote><blockquote type="cite"><span>- so we should be able to reuse that code. It might not be a straight</span><br></blockquote><blockquote type="cite"><span>copy and paste, but the bulk of the work is ready and done...</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>PRs welcome!</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Thanks,</span><br></blockquote><blockquote type="cite"><span>Ian</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>On 16 November 2017 at 20:54, Kevin Lundberg via swift-corelibs-dev</span><br></blockquote><blockquote type="cite"><span><<a href="mailto:swift-corelibs-dev@swift.org">swift-corelibs-dev@swift.org</a>> wrote:</span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>I’m trying to port some mac/iOS swift code over to also compile and run on linux. However one of the files I’m working with references PropertyListDecoder in order to decode some propertylist data we have in our library, and it’s failing to compile since PropertyListDecoder doesn’t appear to be implemented in the corelibs-foundation project. Is this an oversight, or intentional? Are there any workarounds I can do (short of re-encoding our data in JSON which i’d prefer not to do) to get access to property list decoding on linux?</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Thanks!</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>--</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Kevin Lundberg</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>_______________________________________________</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>swift-corelibs-dev mailing list</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span><a href="mailto:swift-corelibs-dev@swift.org">swift-corelibs-dev@swift.org</a></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span><a href="https://lists.swift.org/mailman/listinfo/swift-corelibs-dev">https://lists.swift.org/mailman/listinfo/swift-corelibs-dev</a></span><br></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>-- </span><br></blockquote><blockquote type="cite"><span>Ian Partridge</span><br></blockquote><span></span><br><span>_______________________________________________</span><br><span>swift-corelibs-dev mailing list</span><br><span><a href="mailto:swift-corelibs-dev@swift.org">swift-corelibs-dev@swift.org</a></span><br><span><a href="https://lists.swift.org/mailman/listinfo/swift-corelibs-dev">https://lists.swift.org/mailman/listinfo/swift-corelibs-dev</a></span><br></div></blockquote></div></div></body></html>