, _ args: CVaListPointer)
If that's still correct, then I guess that's what we should be adding
Chris
From: Luke Howard
To: Chris Bailey/UK/IBM@IBMGB
Cc: Tony Parker ,
swift-corelibs-dev@swift.org
Date: 06/07/2016 12:31
Subject: Re: [swift-corelibs-dev] Query on NSLog
> So for consistency it would make sense to expose it on other platforms as
> well.
>
> Chris
>
>
>
>
> From:Tony Parker via swift-corelibs-dev
>
> To:Luke Howard
> Cc:swift-corelibs-dev@swift.org
> Date: 06/07
platforms as
well.
Chris
From: Tony Parker via swift-corelibs-dev
To: Luke Howard
Cc: swift-corelibs-dev@swift.org
Date: 06/07/2016 00:57
Subject:Re: [swift-corelibs-dev] Query on NSLog
Sent by:swift-corelibs-dev-boun...@swift.org
Frankly, I think I just forgot to put
Frankly, I think I just forgot to put a stub for it when we put out the first
set of APIs.
- Tony
> On Jul 5, 2016, at 4:54 PM, Luke Howard wrote:
>
> I added NSLog for NSKeyedArchiver so the output formatting would more closely
> match Darwin, but I punted whether to make it public.
>
>> On
I added NSLog for NSKeyedArchiver so the output formatting would more closely
match Darwin, but I punted whether to make it public.
> On 6 Jul 2016, at 5:42 AM, Tony Parker via swift-corelibs-dev
> wrote:
>
> Hi Sai,
>
> Out of curiosity, why NSLog instead of Swift’s print function?
>
> - To
Hi Sai,
Out of curiosity, why NSLog instead of Swift’s print function?
- Tony
> On Jun 27, 2016, at 4:37 AM, Sai Kanduri via swift-corelibs-dev
> wrote:
>
> Hi All,
>
> Currently NSLog has only one internal function NSLog() which can be used
> only by Foundation classes.Can this be made
