*mumble* damnit jordan this requires libdispatch *mumble*
-a
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Adrian Chadd wrote
in :
ad> On 19 December 2016 at 16:04, Jordan Hubbard
wrote:
ad> >
ad> > On Dec 19, 2016, at 12:27 PM, Adrian Chadd wrote:
ad> >
ad> > So although I like the sentiment, I don't think using dtrace for
ad> > program logging is the right answer. I like what apple did to wrap
> On Dec 19, 2016, at 12:27 PM, Adrian Chadd wrote:
>
> So although I like the sentiment, I don't think using dtrace for
> program logging is the right answer. I like what apple did to wrap
> the program logging stuff so people didn't just write their own
> libraries (hi!) and so there's a unif
On 19 December 2016 at 16:04, Jordan Hubbard wrote:
>
> On Dec 19, 2016, at 12:27 PM, Adrian Chadd wrote:
>
> So although I like the sentiment, I don't think using dtrace for
> program logging is the right answer. I like what apple did to wrap
> the program logging stuff so people didn't just wr
Hi,
I'd love to see a unified-ish logging API for FreeBSD applications. I
always end up reusing some C code I have here that I based on some
Squid style logging API in ages past. I could always polish it up and
put it up for review.
I'm not a big fan of requiring dtrace to use it though. On a lot
