Good idea, I filed a bug for that here.

https://bugs.swift.org/browse/SR-59 <https://bugs.swift.org/browse/SR-59>

- Tony

> On Dec 4, 2015, at 12:49 PM, Tom Leavy <t...@wickr.com> wrote:
> 
> Hey Tony,
> 
> That sounds like a good objective overall, thanks for clarifying. I think you 
> guys should write that someplace in the documentation on github (if it hasn’t 
> been already)
> 
> Thomas Leavy | Wickr Inc.
> VP Mobile Applications, Architecture | Newark, NJ
> 
> 
>> On Dec 4, 2015, at 2:39 PM, anthony.par...@apple.com wrote:
>> 
>> Hi Tom,
>> 
>> I believe it’s important for us to keep our dependencies to an absolute 
>> minimum for the core libraries, since they will be distributed very widely. 
>> I would prefer to have our own implementation of the JSON parser in 
>> Foundation rather than use one from another project.
>> 
>> The one from Darwin is about 2k lines of Objective-C (actually, mostly C).
>> 
>> - Tony
>> 
>>> On Dec 4, 2015, at 11:21 AM, Tom Leavy <t...@wickr.com> wrote:
>>> 
>>> I was wondering what the official position on introducing dependencies 
>>> currently is. I would love to contribute an implementation of 
>>> NSJSONSerialization. I already have written a wrapper that uses yajl to 
>>> take a CFDictionaryRef or CFArrayRef and encodes them into CFDataRef or 
>>> CFStringRef JSON values.. Is it acceptable to use yajl and introduce a 
>>> dependency, or is it a goal of the foundation project to supply its own 
>>> implementation of a JSON parser?
>>> This e-mail message is intended only for the named recipient(s) above and 
>>> is covered by the Electronic Communications Privacy Act 18 U.S.C. Section 
>>> 2510-2521. This e-mail is confidential and may contain information that is 
>>> privileged or exempt from disclosure under applicable law. If you have 
>>> received this message in error please immediately notify the sender by 
>>> return e-mail and delete this e-mail message from your computer, mobile 
>>> devices and any cloud storage backup systems as well as destroy any printed 
>>> copy you might have made.
>>> 
>>> _______________________________________________
>>> swift-corelibs-dev mailing list
>>> swift-corelibs-dev@swift.org
>>> https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
>> 
> 
> 
> This e-mail message is intended only for the named recipient(s) above and is 
> covered by the Electronic Communications Privacy Act 18 U.S.C. Section 
> 2510-2521. This e-mail is confidential and may contain information that is 
> privileged or exempt from disclosure under applicable law. If you have 
> received this message in error please immediately notify the sender by return 
> e-mail and delete this e-mail message from your computer, mobile devices and 
> any cloud storage backup systems as well as destroy any printed copy you 
> might have made.

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

Reply via email to