[swift-evolution] The great renaming and the state of new Unified Logging in Swift

Zach Waldowski zach at waldowski.me
Tue Sep 6 10:05:03 CDT 2016


For a wrapper, are there any public hooks into dyld that allow us to do
anything meaningful with #dsoHandle on prior OS? Without that, and
without using #dsoHandle, wrapping os_log is essentially useless.

Cheers!
  Zachary Waldowski
  zach at waldowski.me


On Mon, Sep 5, 2016, at 10:59 AM, Douglas Gregor via swift-evolution wrote:
>
>
> Sent from my iPhone
>
> On Sep 4, 2016, at 11:48 PM, Goffredo Marocchi
> <panajev at gmail.com> wrote:
>> Hey Doug,
>>
>> How do I use it in Swift code without a wrapper, which is
>> understandably a bit pointless, if I still support iOS 9?
>
> #if or a wrapper are your best options.
>
>   - Doug
>
>>
>> Sent from my iPhone
>>
>> On 5 Sep 2016, at 05:05, Brandon Knope via swift-evolution <swift-
>> evolution at swift.org> wrote:
>>> Where should the lack of {public} be reported then?
>>>
>>> This seems like it falls under jira and not radar because it's in
>>> swift open source but I'm not 100 percent
>>>
>>> Brandon
>>>
>>> Sent from my iPad
>>>
>>> On Sep 4, 2016, at 11:48 PM, Douglas Gregor <dgregor at apple.com>
>>> wrote:
>>>>
>>>>
>>>> Sent from my iPhone
>>>>
>>>> On Sep 3, 2016, at 11:32 AM, Ben Rimmington via swift-evolution <swift-
>>>> evolution at swift.org> wrote:
>>>>>
>>>>>> On 3 Sep 2016, at 19:13, Brandon Knope <bknope at me.com> wrote:
>>>>>>
>>>>>> Thank you! I was looking for this last night and failed.
>>>>>>
>>>>>> Why do you think {public} isn't included?
>>>>>
>>>>> I don't know, but trying to reimplement __builtin_os_log_format in
>>>>> the overlay seems wrong. It would be better to have a variant of
>>>>> __builtin_os_log_format which takes a va_list.
>>>>
>>>>
>>>> __builtin_os_log_format is implemented by Clang, not a library, and
>>>> is quite involved. Implementing os_log in an overlay to provide
>>>> near feature-compatibility with the C API is the right approach for
>>>> Swift 3, where a more comprehensive solution (say, a general
>>>> logging API based on string interpolation or similar) is way out of
>>>> scope.
>>>>
>>>>   - Doug
>>>>
>>>>
>>>>>
>>>>> -- Ben
>>>>>
>>>>> _______________________________________________
>>>>> swift-evolution mailing list
>>>>> swift-evolution at swift.org
>>>>> https://lists.swift.org/mailman/listinfo/swift-evolution
>>> _______________________________________________
>>> swift-evolution mailing list
>>> swift-evolution at swift.org
>>> https://lists.swift.org/mailman/listinfo/swift-evolution
> _________________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160906/9f20de27/attachment.html>


More information about the swift-evolution mailing list