Re: [swift-corelibs-dev] PropertyListDecoder/Encoder?

2017-11-16 Thread Luke Howard via swift-corelibs-dev
https://github.com/apple/swift-corelibs-foundation/pull/1237

May/may not be useful - unfortunately couldn’t get it working on Linux so had 
to close.

Sent from my iPhone

> On 16 Nov 2017, at 21:18, Kevin Lundberg via swift-corelibs-dev 
>  wrote:
> 
> 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).
> --
> Kevin Lundberg
> 
> 
> 
>> On Nov 16, 2017, at 4:12 PM, Ian Partridge  wrote:
>> 
>> Hi Kevin,
>> 
>> It's unintentional, in the sense that noone has done the work yet to
>> implement the PropertyListDecoder in corelibs-foundation.
>> 
>> However, the Darwin implementation is actually open source - see
>> https://github.com/apple/swift/blob/master/stdlib/public/SDK/Foundation/PlistEncoder.swift
>> - so we should be able to reuse that code. It might not be a straight
>> copy and paste, but the bulk of the work is ready and done...
>> 
>> PRs welcome!
>> 
>> Thanks,
>> Ian
>> 
>> On 16 November 2017 at 20:54, Kevin Lundberg via swift-corelibs-dev
>>  wrote:
>>> 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?
>>> 
>>> Thanks!
>>> 
>>> --
>>> Kevin Lundberg
>>> 
>>> 
>>> 
>>> ___
>>> swift-corelibs-dev mailing list
>>> swift-corelibs-dev@swift.org
>>> https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
>> 
>> 
>> 
>> -- 
>> Ian Partridge
> 
> ___
> swift-corelibs-dev mailing list
> 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


Re: [swift-corelibs-dev] PropertyListDecoder/Encoder?

2017-11-16 Thread Kevin Lundberg via swift-corelibs-dev
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).
--
Kevin Lundberg



> On Nov 16, 2017, at 4:12 PM, Ian Partridge  wrote:
> 
> Hi Kevin,
> 
> It's unintentional, in the sense that noone has done the work yet to
> implement the PropertyListDecoder in corelibs-foundation.
> 
> However, the Darwin implementation is actually open source - see
> https://github.com/apple/swift/blob/master/stdlib/public/SDK/Foundation/PlistEncoder.swift
> - so we should be able to reuse that code. It might not be a straight
> copy and paste, but the bulk of the work is ready and done...
> 
> PRs welcome!
> 
> Thanks,
> Ian
> 
> On 16 November 2017 at 20:54, Kevin Lundberg via swift-corelibs-dev
>  wrote:
>> 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?
>> 
>> Thanks!
>> 
>> --
>> Kevin Lundberg
>> 
>> 
>> 
>> ___
>> swift-corelibs-dev mailing list
>> swift-corelibs-dev@swift.org
>> https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
> 
> 
> 
> -- 
> Ian Partridge

___
swift-corelibs-dev mailing list
swift-corelibs-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-corelibs-dev


Re: [swift-corelibs-dev] PropertyListDecoder/Encoder?

2017-11-16 Thread Ian Partridge via swift-corelibs-dev
Hi Kevin,

It's unintentional, in the sense that noone has done the work yet to
implement the PropertyListDecoder in corelibs-foundation.

However, the Darwin implementation is actually open source - see
https://github.com/apple/swift/blob/master/stdlib/public/SDK/Foundation/PlistEncoder.swift
- so we should be able to reuse that code. It might not be a straight
copy and paste, but the bulk of the work is ready and done...

PRs welcome!

Thanks,
Ian

On 16 November 2017 at 20:54, Kevin Lundberg via swift-corelibs-dev
 wrote:
> 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?
>
> Thanks!
>
> --
> Kevin Lundberg
>
>
>
> ___
> swift-corelibs-dev mailing list
> swift-corelibs-dev@swift.org
> https://lists.swift.org/mailman/listinfo/swift-corelibs-dev



-- 
Ian Partridge
___
swift-corelibs-dev mailing list
swift-corelibs-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-corelibs-dev


[swift-corelibs-dev] PropertyListDecoder/Encoder?

2017-11-16 Thread Kevin Lundberg via swift-corelibs-dev
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?

Thanks!

--
Kevin Lundberg



___
swift-corelibs-dev mailing list
swift-corelibs-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-corelibs-dev