Andrei Alexandrescu wrote:
Graham Fawcett wrote:
Hi Andrei,
On Wed, 12 May 2010 09:43:00 -0700, Andrei Alexandrescu wrote:
strtr wrote:
sybrandy Wrote:
Hello,
I just wanted to let everyone know that I created a simple logging
library for D. I wrote it as I wanted to debug my programs without
having to deal with standard output and have used it for several
little coding adventures.
https://launchpad.net/dlogger
The main features are:
- Supports trace, info, dbug (debug), error, and fatal log errors. -
Logging levels can be changed while the program is running - Is thread
safe (hopefully)
- If compiled with -version=nologger, it's like you never included it.
Besides satisfying my own needs, I felt that a logging library of some
sort would be good for Phobos, hence why I'm making this available.
Please report any issues/suggestions to the launchpad site.
Enjoy!
Casey
I'm pro a std.log (for D1 as well :)
but shouldn't this be in .announce ?
Me too, but unfortunately the logger is using std.stream, which I think
needs replacement.
Comments like this make me nervous. :)
How much of the stdlib do you think needs replacement? Which if any
modules should be considered stable? Can D2 users expect that the
stdlib in a year's time will look anything like it does now? Is there
a formal development plan?
I appreciate that D2 and its Phobos are works in progress. But I would
hope that a statement like "std.stream needs replacement," coming from
a core developer, would be followed up with either a replacement plan
or a rationale and a call-to-arms. Noblesse oblige!
Perhaps the D2 stdlib documentation should remind prominently that the
stdlib isn't actually standardized yet, and that it should be treated
as an experimental library.
Best,
Graham
I understand. The word about std.stream has been out for a long time,
and there is no similarly large overhaul planned to other parts of Phobos.
But there is a large number of modules scheduled for deprecation
(std.boxer, for example). I really like the idea of having a STATUS
statement displayed at the top of the docs for every module.
