<div dir="ltr">I have used Lumberjack[1] with Objective-C and I found it pretty good. Maybe it's scope is too large for the standard library, but it could serve as a good reference.<div><br></div><div>[1] - <a href="https://github.com/CocoaLumberjack/CocoaLumberjack">https://github.com/CocoaLumberjack/CocoaLumberjack</a></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Dec 6, 2015 at 12:54 AM, Alexander Kolov via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Hi everyone,<div><br></div><div>Coming from a short discussion in swift-corelibs-dev, I’m investigating the need of a standard logging API as a part of core libraries.</div><div><br></div><div>The motivation behind this would be having a unified and configurable set of APIs between all first-party modules and third party applications and libraries.</div><div>I think this will help each of us since right now we’re inventing our own solutions as well many bigger third-party library providers have formats and facilities of their own.</div><div><br></div><div>As I currently see it would be somewhat similar to python logging and possibly even structlog (<a href="http://www.structlog.org/en/stable/" target="_blank">http://www.structlog.org/en/stable/</a>), with configurable formatters and handlers, including and not limited to remote loggers and syslog support.</div><div><br></div><div>I’d love to hear your opinions and feedback on this and possibly start with some more formalized proposal and implementation if there’s enough support and need.</div><div><br></div><div>Thanks,</div><div>Alex</div><div><br></div><div><br></div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=-2ByAk-2F7E-2FiEEGTs1FrlcDxdE6xHy0RVS34uokvNmIAbYFwrtSodToM0ehGnCwhob1Uw83Gf4-2Fq8BojM8QieRJymHsDhQuq2fTfmMr3wwuERwTzULn-2BWKfyzl8472jIVX0zGUZUlBqzFYCvTwKtQ-2FgxqOazDBNFZiT9JKcJ8mmTyZ8IybiV9rTDQpfKHUCnaMpYzJ7fQfrxzUFmvOhMrl6MKQ9DEUNn8Rss-2Bru3js34OA-3D" alt="" width="1" height="1" border="0" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important">
</div>
<br>_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Warm regards<br>Roshan<br></div>
</div>