Re: [swift-corelibs-dev] Third party license compatible libraries for JSON

[swizzlr]

Sorry, forgot to include the link:

http://zserge.com/jsmn.html
> On 4 Dec 2015, at 13:33, swizzlr  wrote:
> 
> I would like to begin work on implementing NSJSONSerialization. I believe 
> that to get this up and running quickly, it would be prudent to vendor jsmn 
> () within Foundation so we can quickly provide an implementation which will 
> be crucial to web server support, instead of writing our own tokenizer in 
> Swift, though this would definitely be a worthwhile long term goal.
> 
> My questions are:
> 
> Would it be appropriate to vendor this library either as a static lib, or 
> even better, within the target itself?
> Would there be an objection to adding MIT licensed code to the OSS Foundation?
> 
> If the answer to these questions is yes, then I will begin immediately, but 
> I’d like to hear from someone in the core team about it.
> 
> Best,
> 
> Tom

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

[swift-corelibs-dev] Third party license compatible libraries for JSON

[swizzlr]

I would like to begin work on implementing NSJSONSerialization. I believe that 
to get this up and running quickly, it would be prudent to vendor jsmn () 
within Foundation so we can quickly provide an implementation which will be 
crucial to web server support, instead of writing our own tokenizer in Swift, 
though this would definitely be a worthwhile long term goal.

My questions are:

Would it be appropriate to vendor this library either as a static lib, or even 
better, within the target itself?
Would there be an objection to adding MIT licensed code to the OSS Foundation?

If the answer to these questions is yes, then I will begin immediately, but I’d 
like to hear from someone in the core team about it.

Best,

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

Re: [swift-corelibs-dev] swift-corelibs-dev Digest, Vol 1, Issue 18

[swizzlr]

While I totally agree that that is a great long term goal, getting Swift 
running JSON parsing on the server as fast as humanly possible is a priority 
for many people. Would it be acceptable to vendor a minimal JSON tokenizer like 
jsmn to handle the brunt of the implementation, until such time as we can write 
one ourselves?

Tom, I’d love to collaborate with you on NSJSONSerialization and take some 
ownership of enhancing this crucial slice of Foundation. It’ll touch on many 
aspects of Foundation’s data types and as such will make a great platform for 
unearthing bugs elsewhere and serving as an integration test.

Thomas

> On 4 Dec 2015, at 21:09, swift-corelibs-dev-requ...@swift.org wrote:
> 
> Send swift-corelibs-dev mailing list submissions to
>   swift-corelibs-dev@swift.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>   https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
> or, via email, send a message with subject or body 'help' to
>   swift-corelibs-dev-requ...@swift.org
> 
> You can reach the person managing the list at
>   swift-corelibs-dev-ow...@swift.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of swift-corelibs-dev digest..."
> 
> 
> Today's Topics:
> 
>   1. Re: Rules on adding dependencies (Tom Leavy)
>   2. Re: Rules on adding dependencies (Tony Parker)
> 
> 
> --
> 
> Message: 1
> Date: Fri, 4 Dec 2015 21:01:43 +
> From: Tom Leavy 
> To: "anthony.par...@apple.com" 
> Cc: "swift-corelibs-dev@swift.org" 
> Subject: Re: [swift-corelibs-dev] Rules on adding dependencies
> Message-ID: <60882613-69f6-4f75-9fde-aace85ea7...@wickr.com>
> Content-Type: text/plain; charset="utf-8"
> 
> Thanks!
> 
> Is there a list of current dependencies someplace? I understand you use a 
> specific version of ICU as part of CoreFoundation.
> 
> Thomas Leavy | Wickr Inc.
> VP Mobile Applications, Architecture | Newark, NJ
> 
> 
> On Dec 4, 2015, at 3:52 PM, 
> anthony.par...@apple.com wrote:
> 
> Good idea, I filed a bug for that here.
> 
> https://bugs.swift.org/browse/SR-59
> 
> - Tony
> 
> On Dec 4, 2015, at 12:49 PM, Tom Leavy 
> mailto: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 
> mailto: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.
> 
> 
> 
> This e-mail mes