> On Oct 26, 2016, at 10:14 AM, Max Desiatov <max.desia...@gmail.com> wrote: > > Hi Tony, > > This is very interesting caveat. Is there a plan to get this documented > anywhere? I haven't seen any documentation for Swift Foundation published > publicly anywhere akin to how it's done for other APIs at > https://developer.apple.com/reference/ > <https://developer.apple.com/reference/>. > > With best regards, Max.
With respect to the NSObject requirement: It’s really more of a known issue than a permanent limitation. To over summarize the situation: NSKeyedArchiver (the Objective-C one) puts a private category on NSObject and assumes all objects respond to those messages after that. We don’t really have documentation for swift-corelibs-foundation beyond what we can put in our own headerdoc format there. That would be something I would really appreciate help on if anyone is interested in contributing. - Tony > >> On 26 Oct 2016, at 18:11, Tony Parker via swift-corelibs-dev >> <swift-corelibs-dev@swift.org <mailto:swift-corelibs-dev@swift.org>> wrote: >> >> Hi Sai, >> >> We do have basic support for keyed archiving and unarchiving in >> swift-corelibs-foundation on Linux. The limitation is that the NSCoding >> protocol cannot be applied to Swift struct types, only class types. On >> Darwin, the class also must be a subclass of NSObject. This last limitation >> may not exist on Linux, but you should be aware that if you encode a >> non-NSObject subclass on Linux then you would not be able to decode it on >> Darwin. >> >> - Tony >> >>> On Oct 26, 2016, at 4:07 AM, Sai Kanduri via swift-corelibs-dev >>> <swift-corelibs-dev@swift.org <mailto:swift-corelibs-dev@swift.org>> wrote: >>> >>> Hi Tony, >>> >>> From your comments on Pull Request #574 I understand that we cannot >>> archive/un-archive non-NS objects using NsKeyedArchiver & >>> NSKeyedUnarchiver.I s my understanding correct ..? Does this means that >>> archiving and un-archiving of swift types is not supported on Linux ? >>> >>> -Sai Hema >>> >>> _______________________________________________ >>> swift-corelibs-dev mailing list >>> swift-corelibs-dev@swift.org <mailto:swift-corelibs-dev@swift.org> >>> https://lists.swift.org/mailman/listinfo/swift-corelibs-dev >>> <https://lists.swift.org/mailman/listinfo/swift-corelibs-dev> >> >> _______________________________________________ >> swift-corelibs-dev mailing list >> swift-corelibs-dev@swift.org <mailto:swift-corelibs-dev@swift.org> >> https://lists.swift.org/mailman/listinfo/swift-corelibs-dev >
_______________________________________________ swift-corelibs-dev mailing list swift-corelibs-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
