> On 22 Dec 2015, at 5:50 AM, Jordan Rose wrote:
>
> IMHO on Linux NSKeyedArchiver should always use mangled names. If we want
> cross-platform archives, we should set up standard substitutions, but given
> that Swift classes exposed to Objective-C are archived with their full names
> it does
Also, I’m sure this is just my lack of Swift-fu but I’m occasionally getting
EXC_BAD_INSTRUCTION in NSString.hash() where the hash code is cast to an Int.
If I use unsafeBitCast() instead it seems to work, but I have no idea whether
this is safe or not.
I’m on OS X with the 2015-12-18 snapshot.
To clarify the goals: I think it is reasonable for us to have a goal to be able
to encode/decode archives from foreign targets; e.g. linux encodes an archive
and mac os x decodes or iOS encodes and linux decodes. This will allow for
server architecture to transmit binary archives across the wire
> On 23 Dec 2015, at 5:16 AM, Philippe Hausler wrote:
>
>> BTW I found a couple of small CF nits:
>>
>> * in CFDictionaryGetKeysAndValues(), keybuf and valuebuf are transposed in
>> the call to CF_SWIFT_FUNCDISPATCHV(NSDictionary.getObjects())
>>
>> * _CFSwiftDictionaryGetKeysAndValues() does
Hello all,
I've been referring to the project hosted at
https://github.com/apple/swift-corelibs-xctest as
"swift-corelibs-xctest", and the project shipped alongside Xcode 7.2
as "Apple XCTest".
What are the canonical names for these projects? I'd like to agree on
common terminology to avoid confu
Some work on NSKeyedArchiver below:
https://github.com/lhoward/swift-corelibs-foundation/tree/lhoward/nscoding
Very incomplete (most classes don’t have coders, there is no unarchiver,
inexperienced Swift programmer).
— Luke
___
swift-corelibs-dev mail
