On 2011-05-28 10:30, Jose Armando Garcia wrote:
> The implementation and documentation for std.log is ready for viewing.
> You can take a look at the doc at
> http://jsancio.github.com/phobos/phobos/std_log.html. The source code
> is at https://github.com/jsancio/phobos/blob/master/std/log.d.
>
>
Am 28.05.2011 20:19, schrieb Andrej Mitrovic:
On 5/28/11, Daniel Gibson wrote:
Am 28.05.2011 20:08, schrieb Andrej Mitrovic:
Clever use of __FILE__ and __LINE__ to create unique instantiations of
the every() template. :)
does this belong in this thread?
I was just commenting the implementa
On 5/28/11, Daniel Gibson wrote:
> Am 28.05.2011 20:08, schrieb Andrej Mitrovic:
>> Clever use of __FILE__ and __LINE__ to create unique instantiations of
>> the every() template. :)
>
> does this belong in this thread?
I was just commenting the implementation.
Am 28.05.2011 20:08, schrieb Andrej Mitrovic:
Clever use of __FILE__ and __LINE__ to create unique instantiations of
the every() template. :)
does this belong in this thread?
furthermore __FILE__ and __LINE__ isn't enough for every(...) ; every(...);
Clever use of __FILE__ and __LINE__ to create unique instantiations of
the every() template. :)
The implementation and documentation for std.log is ready for viewing.
You can take a look at the doc at
http://jsancio.github.com/phobos/phobos/std_log.html. The source code
is at https://github.com/jsancio/phobos/blob/master/std/log.d.
I had to make some changes to druntime to get the thread id
Jose Armando Garcia wrote:
>Just wanted to let everyone know that I am working on having a review
>wordy std.log. I am almost done with the implementation. I am
>currently working on improving the documentation. Is there a link that
>describes the review process. I would like to get std.log as clos
Just wanted to let everyone know that I am working on having a review
wordy std.log. I am almost done with the implementation. I am
currently working on improving the documentation. Is there a link that
describes the review process. I would like to get std.log as close to
final to minimize the back
On Sun, 22 May 2011 21:38:26 +0300, Lars T. Kyllingstad
wrote:
On Sun, 15 May 2011 17:15:38 +0200, Jacob Carlborg wrote:
Why does the user have to manually initialize the library? Why not use a
static constructor or lazy initialization?
Actually I don't like it at all, that the logging li
On Sun, 15 May 2011 17:15:38 +0200, Jacob Carlborg wrote:
> On 2011-05-14 19:04, Andrei Alexandrescu wrote:
>> On 5/9/11 1:52 AM, Andrei Alexandrescu wrote: [snip]
>>
>> I updated my std.log draft. Added a lot of features including formatted
>> writing, delayed logging, and a variety of configurat
On 5/19/11 2:56 AM, Jens Mueller wrote:
Andrei Alexandrescu wrote:
* The way I see a nice implementation would be (inspired from Jens'
work) via a class that defines the client-level methods as final,
and has 2-3 extension methods that do the work. That way there's no
need for awkward extra name
Andrei Alexandrescu wrote:
> On 5/18/11 8:00 AM, Jose Armando Garcia wrote:
> >I also think that having competing logging module is a good thing.
> >This process will result in a better module for phobos and as a result
> >a better module for the user.
>
> Clearly there are advantages to competing
On 5/18/11 8:00 AM, Jose Armando Garcia wrote:
I also think that having competing logging module is a good thing.
This process will result in a better module for phobos and as a result
a better module for the user.
Clearly there are advantages to competing proposals, but I have mixed
feelings
This is a review of std.log. Overall, I really like the API exposed by
this module because it allows efficient compile time and run time
configuration. I have limited the review to the API and how the API
affects the implementation. I will review the implementation once the
API is close to final.
std.logging is still alive! After posting my first attempt at a
logging module I went back and spent a lot of time on how I could
improve the API. I would like to say that Andrei's std.log module had
a great influence on the final outcome. There are some aspect of
std.log's API that I really like.
On 2011-05-17 22:15, Andrei Alexandrescu wrote:
On 5/17/11 4:02 AM, Jacob Carlborg wrote:
On 2011-05-16 02:05, Andrei Alexandrescu wrote:
Thanks for your work.
I think there's an important distinction to be made. There are two
"API"s being discussed. One is the client interface and the other i
On 5/17/11 4:02 AM, Jacob Carlborg wrote:
On 2011-05-16 02:05, Andrei Alexandrescu wrote:
Thanks for your work.
I think there's an important distinction to be made. There are two
"API"s being discussed. One is the client interface and the other is the
extensibility interface.
Jose looked into
On 2011-05-16 02:05, Andrei Alexandrescu wrote:
Thanks for your work.
I think there's an important distinction to be made. There are two
"API"s being discussed. One is the client interface and the other is the
extensibility interface.
Jose looked into both: he provided a client interface that h
On 2011-05-16 01:27, Jonathan M Davis wrote:
On 2011-05-15 16:01, Andrei Alexandrescu wrote:
On 05/15/2011 10:26 AM, Jacob Carlborg wrote:
On 2011-05-15 00:33, Andrei Alexandrescu wrote:
On 05/14/2011 05:17 PM, Jonathan M Davis wrote:
On 2011-05-14 14:56, Michel Fortin wrote:
On 2011-05-14 1
On 2011-05-16 01:04, Andrei Alexandrescu wrote:
On 05/15/2011 10:22 AM, Jacob Carlborg wrote:
On 2011-05-14 22:37, Andrei Alexandrescu wrote:
I want to nail usability before extension. Extensibility can be provided
via an indirection inside FileLogger (which should indeed receive a more
appropr
Andrei Alexandrescu wrote:
> On 5/9/11 1:52 AM, Andrei Alexandrescu wrote:
> [snip]
>
> I updated my std.log draft. Added a lot of features including
> formatted writing, delayed logging, and a variety of configuration
> options. Replaced the redundant log.xyz with logXyz. The
> implementation is
On 14/05/11 19.04, Andrei Alexandrescu wrote:
On 5/9/11 1:52 AM, Andrei Alexandrescu wrote:
[snip]
I updated my std.log draft. Added a lot of features including formatted
writing, delayed logging, and a variety of configuration options.
Replaced the redundant log.xyz with logXyz. The implementat
On 05/15/2011 02:54 PM, Jacob Carlborg wrote:
On 2011-05-14 19:04, Andrei Alexandrescu wrote:
On 5/9/11 1:52 AM, Andrei Alexandrescu wrote:
[snip]
I updated my std.log draft. Added a lot of features including formatted
writing, delayed logging, and a variety of configuration options.
Replaced t
On 2011-05-15 16:01, Andrei Alexandrescu wrote:
> On 05/15/2011 10:26 AM, Jacob Carlborg wrote:
> > On 2011-05-15 00:33, Andrei Alexandrescu wrote:
> >> On 05/14/2011 05:17 PM, Jonathan M Davis wrote:
> >>> On 2011-05-14 14:56, Michel Fortin wrote:
> On 2011-05-14 17:31:30 -0400, Jonathan M Da
On 05/15/2011 10:22 AM, Jacob Carlborg wrote:
On 2011-05-14 22:37, Andrei Alexandrescu wrote:
I want to nail usability before extension. Extensibility can be provided
via an indirection inside FileLogger (which should indeed receive a more
appropriate name).
Andrei
The obvious solution would
On 05/15/2011 10:26 AM, Jacob Carlborg wrote:
On 2011-05-15 00:33, Andrei Alexandrescu wrote:
On 05/14/2011 05:17 PM, Jonathan M Davis wrote:
On 2011-05-14 14:56, Michel Fortin wrote:
On 2011-05-14 17:31:30 -0400, Jonathan M Davis
said:
So, I do think that knowing which thread is logging what
On 05/15/2011 10:53 AM, Jens Mueller wrote:
Andrei Alexandrescu wrote:
On 05/14/2011 04:56 PM, Michel Fortin wrote:
On 2011-05-14 17:31:30 -0400, Jonathan M Davis said:
So, I do think that knowing which thread is logging what could be very
important for some programs, but I don't think that
On 2011-05-14 19:04, Andrei Alexandrescu wrote:
On 5/9/11 1:52 AM, Andrei Alexandrescu wrote:
[snip]
I updated my std.log draft. Added a lot of features including formatted
writing, delayed logging, and a variety of configuration options.
Replaced the redundant log.xyz with logXyz. The implement
Andrei Alexandrescu wrote:
> On 05/14/2011 04:56 PM, Michel Fortin wrote:
> >On 2011-05-14 17:31:30 -0400, Jonathan M Davis said:
> >
> >>So, I do think that knowing which thread is logging what could be very
> >>important for some programs, but I don't think that separating the log
> >>files
> >>
On 15/05/2011 16:15, Jacob Carlborg wrote:
On 2011-05-14 19:04, Andrei Alexandrescu wrote:
On 5/9/11 1:52 AM, Andrei Alexandrescu wrote:
[snip]
I updated my std.log draft. Added a lot of features including formatted
writing, delayed logging, and a variety of configuration options.
Replaced the
On 2011-05-15 00:33, Andrei Alexandrescu wrote:
On 05/14/2011 05:17 PM, Jonathan M Davis wrote:
On 2011-05-14 14:56, Michel Fortin wrote:
On 2011-05-14 17:31:30 -0400, Jonathan M Davis
said:
So, I do think that knowing which thread is logging what could be very
important for some programs, but
On 2011-05-14 22:37, Andrei Alexandrescu wrote:
On 05/14/2011 02:50 PM, Robert Clipsham wrote:
On 14/05/2011 18:04, Andrei Alexandrescu wrote:
On 5/9/11 1:52 AM, Andrei Alexandrescu wrote:
[snip]
I updated my std.log draft. Added a lot of features including formatted
writing, delayed logging,
On 2011-05-14 19:04, Andrei Alexandrescu wrote:
On 5/9/11 1:52 AM, Andrei Alexandrescu wrote:
[snip]
I updated my std.log draft. Added a lot of features including formatted
writing, delayed logging, and a variety of configuration options.
Replaced the redundant log.xyz with logXyz. The implement
On 2011-05-14 10:04, Andrei Alexandrescu wrote:
> On 5/9/11 1:52 AM, Andrei Alexandrescu wrote:
> [snip]
>
> I updated my std.log draft. Added a lot of features including formatted
> writing, delayed logging, and a variety of configuration options.
> Replaced the redundant log.xyz with logXyz. The
On 5/14/11 7:13 PM, Brad Roberts wrote:
On 5/14/2011 3:35 PM, Andrei Alexandrescu wrote:
On 05/14/2011 04:56 PM, Michel Fortin wrote:
On 2011-05-14 17:31:30 -0400, Jonathan M Davis said:
So, I do think that knowing which thread is logging what could be very
important for some programs, but I
On 5/14/11 6:43 PM, Michel Fortin wrote:
On 2011-05-14 18:35:32 -0400, Andrei Alexandrescu
said:
On 05/14/2011 04:56 PM, Michel Fortin wrote:
I'll also question whether they should be written to files at all by
default (as opposed to stdin and stderr). I'm aware initLogging's
documentation sa
On 5/14/11 6:35 PM, Michel Fortin wrote:
On 2011-05-14 13:04:54 -0400, Andrei Alexandrescu
said:
Documentation:
http://d-programming-language.org/phobos-prerelease/std_log.html
Source:
https://github.com/andralex/phobos
Feedback welcome.
Shouldn't "everyMs" and "afterMs" accept any of co
On 2011-05-14 16:35, Michel Fortin wrote:
> On 2011-05-14 13:04:54 -0400, Andrei Alexandrescu
>
> said:
> > Documentation:
> >
> > http://d-programming-language.org/phobos-prerelease/std_log.html
> >
> > Source:
> >
> > https://github.com/andralex/phobos
> >
> > Feedback welcome.
>
> Shouldn
On 2011-05-14 15:33, Andrei Alexandrescu wrote:
> On 05/14/2011 05:17 PM, Jonathan M Davis wrote:
> > On 2011-05-14 14:56, Michel Fortin wrote:
> >> On 2011-05-14 17:31:30 -0400, Jonathan M Davis
said:
> >>> So, I do think that knowing which thread is logging what could be very
> >>> important fo
On 5/14/2011 3:35 PM, Andrei Alexandrescu wrote:
> On 05/14/2011 04:56 PM, Michel Fortin wrote:
>> On 2011-05-14 17:31:30 -0400, Jonathan M Davis said:
>>
>>> So, I do think that knowing which thread is logging what could be very
>>> important for some programs, but I don't think that separating t
On 05/14/2011 06:36 PM, Michel Fortin wrote:
On 2011-05-14 18:33:06 -0400, Andrei Alexandrescu
said:
On 05/14/2011 05:17 PM, Jonathan M Davis wrote:
On 2011-05-14 14:56, Michel Fortin wrote:
I'd even go further and question whether it makes sense to have info,
warning, and errors be written
On 2011-05-14 18:35:32 -0400, Andrei Alexandrescu
said:
On 05/14/2011 04:56 PM, Michel Fortin wrote:
I'll also question whether they should be written to files at all by
default (as opposed to stdin and stderr). I'm aware initLogging's
documentation says: "If logging is effected without ha
On 2011-05-14 13:04:54 -0400, Andrei Alexandrescu
said:
Documentation:
http://d-programming-language.org/phobos-prerelease/std_log.html
Source:
https://github.com/andralex/phobos
Feedback welcome.
Shouldn't "everyMs" and "afterMs" accept any of core.time's duration
types instead of bein
On 2011-05-14 18:33:06 -0400, Andrei Alexandrescu
said:
On 05/14/2011 05:17 PM, Jonathan M Davis wrote:
On 2011-05-14 14:56, Michel Fortin wrote:
I'd even go further and question whether it makes sense to have info,
warning, and errors be written to separate files.
I'd definitely vote for
On 05/14/2011 04:56 PM, Michel Fortin wrote:
On 2011-05-14 17:31:30 -0400, Jonathan M Davis said:
So, I do think that knowing which thread is logging what could be very
important for some programs, but I don't think that separating the log
files
is necessarily a good idea. If you did, you'd lo
On 05/14/2011 05:17 PM, Jonathan M Davis wrote:
On 2011-05-14 14:56, Michel Fortin wrote:
On 2011-05-14 17:31:30 -0400, Jonathan M Davis said:
So, I do think that knowing which thread is logging what could be very
important for some programs, but I don't think that separating the log
files is
On 2011-05-14 14:56, Michel Fortin wrote:
> On 2011-05-14 17:31:30 -0400, Jonathan M Davis said:
> > So, I do think that knowing which thread is logging what could be very
> > important for some programs, but I don't think that separating the log
> > files is necessarily a good idea. If you did, y
Your post just went asian on me. http://i.imgur.com/solwD.png
On 2011-05-14 14:50, Andrei Alexandrescu wrote:
> On 05/14/2011 04:31 PM, Jonathan M Davis wrote:
> > On 2011-05-14 12:36, Andrei Alexandrescu wrote:
> >> On 05/14/2011 01:29 PM, dsimcha wrote:
> >>> On 5/14/2011 1:04 PM, Andrei Alexandrescu wrote:
> On 5/9/11 1:52 AM, Andrei Alexandrescu wrot
On 2011-05-14 17:31:30 -0400, Jonathan M Davis said:
So, I do think that knowing which thread is logging what could be very
important for some programs, but I don't think that separating the log files
is necessarily a good idea. If you did, you'd lose timing information (unless
the time is at t
On 05/14/2011 04:31 PM, Jonathan M Davis wrote:
On 2011-05-14 12:36, Andrei Alexandrescu wrote:
On 05/14/2011 01:29 PM, dsimcha wrote:
On 5/14/2011 1:04 PM, Andrei Alexandrescu wrote:
On 5/9/11 1:52 AM, Andrei Alexandrescu wrote:
[snip]
I updated my std.log draft. Added a lot of features incl
On 2011-05-14 12:36, Andrei Alexandrescu wrote:
> On 05/14/2011 01:29 PM, dsimcha wrote:
> > On 5/14/2011 1:04 PM, Andrei Alexandrescu wrote:
> >> On 5/9/11 1:52 AM, Andrei Alexandrescu wrote:
> >> [snip]
> >>
> >> I updated my std.log draft. Added a lot of features including formatted
> >> writin
On 14/05/2011 21:37, Andrei Alexandrescu wrote:
On 05/14/2011 02:50 PM, Robert Clipsham wrote:
On 14/05/2011 18:04, Andrei Alexandrescu wrote:
On 5/9/11 1:52 AM, Andrei Alexandrescu wrote:
[snip]
I updated my std.log draft. Added a lot of features including formatted
writing, delayed logging,
On 05/14/2011 02:50 PM, Robert Clipsham wrote:
On 14/05/2011 18:04, Andrei Alexandrescu wrote:
On 5/9/11 1:52 AM, Andrei Alexandrescu wrote:
[snip]
I updated my std.log draft. Added a lot of features including formatted
writing, delayed logging, and a variety of configuration options.
Replaced
On 14/05/2011 18:04, Andrei Alexandrescu wrote:
On 5/9/11 1:52 AM, Andrei Alexandrescu wrote:
[snip]
I updated my std.log draft. Added a lot of features including formatted
writing, delayed logging, and a variety of configuration options.
Replaced the redundant log.xyz with logXyz. The implement
On 05/14/2011 01:29 PM, dsimcha wrote:
On 5/14/2011 1:04 PM, Andrei Alexandrescu wrote:
On 5/9/11 1:52 AM, Andrei Alexandrescu wrote:
[snip]
I updated my std.log draft. Added a lot of features including formatted
writing, delayed logging, and a variety of configuration options.
Replaced the red
On 5/14/2011 1:04 PM, Andrei Alexandrescu wrote:
On 5/9/11 1:52 AM, Andrei Alexandrescu wrote:
[snip]
I updated my std.log draft. Added a lot of features including formatted
writing, delayed logging, and a variety of configuration options.
Replaced the redundant log.xyz with logXyz. The implemen
On 5/9/11 1:52 AM, Andrei Alexandrescu wrote:
[snip]
I updated my std.log draft. Added a lot of features including formatted
writing, delayed logging, and a variety of configuration options.
Replaced the redundant log.xyz with logXyz. The implementation is
getting close to reviewable form.
D
On 2011-05-12 05:38, Andrei Alexandrescu wrote:
On 5/11/11 5:09 PM, Sean Kelly wrote:
On May 11, 2011, at 11:38 AM, Jacob Carlborg wrote:
On 2011-05-10 16:41, Andrei Alexandrescu wrote:
On 5/10/11 3:22 AM, Jacob Carlborg wrote:
Are you referring to core.runtime.Runtime.args? That is not comp
On 5/11/11 5:09 PM, Sean Kelly wrote:
On May 11, 2011, at 11:38 AM, Jacob Carlborg wrote:
On 2011-05-10 16:41, Andrei Alexandrescu wrote:
On 5/10/11 3:22 AM, Jacob Carlborg wrote:
Are you referring to core.runtime.Runtime.args? That is not completely
reliable because:
* You can start a new p
On May 11, 2011, at 11:38 AM, Jacob Carlborg wrote:
> On 2011-05-10 16:41, Andrei Alexandrescu wrote:
>> On 5/10/11 3:22 AM, Jacob Carlborg wrote:
>>> Are you referring to core.runtime.Runtime.args? That is not completely
>>> reliable because:
>>>
>>> * You can start a new process, with exec, and
On 2011-05-10 16:41, Andrei Alexandrescu wrote:
On 5/10/11 3:22 AM, Jacob Carlborg wrote:
Are you referring to core.runtime.Runtime.args? That is not completely
reliable because:
* You can start a new process, with exec, and then pass in whatever you
want as the first argument to the process.
On 05/11/2011 09:15 AM, Andrei Alexandrescu wrote:
On 05/11/2011 08:46 AM, dsimcha wrote:
On 5/9/2011 2:52 AM, Andrei Alexandrescu wrote:
As I mentioned I'd already decided I'll take a stab at implementing a
logging module inspired in design from glog. I was tired of the endless
discussions on
On 05/11/2011 08:46 AM, dsimcha wrote:
On 5/9/2011 2:52 AM, Andrei Alexandrescu wrote:
As I mentioned I'd already decided I'll take a stab at implementing a
logging module inspired in design from glog. I was tired of the endless
discussions on what a logging API should look like. This ironically
On 5/9/2011 2:52 AM, Andrei Alexandrescu wrote:
As I mentioned I'd already decided I'll take a stab at implementing a
logging module inspired in design from glog. I was tired of the endless
discussions on what a logging API should look like. This ironically is
leading now to an embarrassment of r
Andrei Alexandrescu wrote:
> On 5/9/11 3:12 PM, Jens Mueller wrote:
> >I think every() behaves strangely. Because the counter is per function.
> >But it should be per logging statement. std.log differs here from glog
> >and this seems incorrect to me. everyMs() has a similar problem.
>
> Actually,
On 5/9/11 3:12 PM, Jens Mueller wrote:
I think every() behaves strangely. Because the counter is per function.
But it should be per logging statement. std.log differs here from glog
and this seems incorrect to me. everyMs() has a similar problem.
Actually, they behave correctly. The counters fo
Thanks! Will do.
On Mon, May 9, 2011 at 4:11 PM, Walter Bright
wrote:
> On 5/7/2011 1:43 PM, Jose Armando Garcia wrote:
>>
>> My intent, and hopefully we will get there with your help, is to
>> include this in Phobos for D2.
>
> Thanks for doing the hard work of designing and laying out an
> impl
On 2011-05-10 16:41, Andrei Alexandrescu wrote:
On 5/10/11 3:22 AM, Jacob Carlborg wrote:
On 2011-05-09 21:18, Andrei Alexandrescu wrote:
On 5/9/11 1:48 PM, Jacob Carlborg wrote:
On 2011-05-09 19:58, Andrei Alexandrescu wrote:
On 5/9/11 12:24 PM, Jacob Carlborg wrote:
I
have a function that
On 5/10/11 3:22 AM, Jacob Carlborg wrote:
On 2011-05-09 21:18, Andrei Alexandrescu wrote:
On 5/9/11 1:48 PM, Jacob Carlborg wrote:
On 2011-05-09 19:58, Andrei Alexandrescu wrote:
On 5/9/11 12:24 PM, Jacob Carlborg wrote:
I
have a function that gets the path of the current process:
http://dso
On 2011-05-09 21:18, Andrei Alexandrescu wrote:
On 5/9/11 1:48 PM, Jacob Carlborg wrote:
On 2011-05-09 19:58, Andrei Alexandrescu wrote:
On 5/9/11 12:24 PM, Jacob Carlborg wrote:
I
have a function that gets the path of the current process:
http://dsource.org/projects/tango/attachment/ticket/1
On 5/9/11, Andrei Alexandrescu wrote:
> One possibility is to provide a nice2ugly template that transforms C#
> format strings into % format strings, e.g. nice2ugly!"{1}:{2}" yields
> the string constant "%1$s:%2$s".
That is exactly what my echo function does. It replaces {} syntax with
%$s synta
On 09/05/2011 20:47, Andrei Alexandrescu wrote:
On 5/9/11 1:34 PM, Robert Clipsham wrote:
That is A LOT nicer to look at. Please can we have this? :<
I, too, prefer it a great deal to the prinf/scanf format, and it
wouldn't be difficult to implement, but at this point we need to worry
about co
Andrei Alexandrescu wrote:
> On 5/7/11 3:43 PM, Jose Armando Garcia wrote:
> >Hey folks,
> >
> >For the past couple of days I took the liberty of partially
> >implementing a logging module for D.
> [snip]
>
> Nice work. Also thanks for contacting me offline.
>
> As I mentioned I'd already decided
On 5/9/11 1:34 PM, Robert Clipsham wrote:
On 09/05/2011 19:18, Andrej Mitrovic wrote:
I'm not a big fan of that format syntax. It's just hard to look at and
figure out what went wrong when things do go wrong.
I'd prefer something like:
https://gist.github.com/963027
But someone would have to i
On 5/9/11 1:48 PM, Jacob Carlborg wrote:
On 2011-05-09 19:58, Andrei Alexandrescu wrote:
On 5/9/11 12:24 PM, Jacob Carlborg wrote:
I
have a function that gets the path of the current process:
http://dsource.org/projects/tango/attachment/ticket/1536/process.d
This links to a file attached to a
On 5/7/2011 1:43 PM, Jose Armando Garcia wrote:
My intent, and hopefully we will get there with your help, is to
include this in Phobos for D2.
Thanks for doing the hard work of designing and laying out an implementation.
Please, though, posting the source code as a news group message is not v
On 5/9/11 1:33 PM, Robert Clipsham wrote:
On 09/05/2011 19:30, Robert Clipsham wrote:
The example looks great, exactly what I'd hope for in the way of a
logging library. A few questions:
* How do you disable logging at compile time? (and is it zero overhead?)
* How do you define your own loggin
On 5/9/11 1:30 PM, Robert Clipsham wrote:
On 09/05/2011 07:52, Andrei Alexandrescu wrote:
On 5/7/11 3:43 PM, Jose Armando Garcia wrote:
Hey folks,
For the past couple of days I took the liberty of partially
implementing a logging module for D.
[snip]
Nice work. Also thanks for contacting me
On 2011-05-09 20:34, Robert Clipsham wrote:
On 09/05/2011 19:18, Andrej Mitrovic wrote:
I'm not a big fan of that format syntax. It's just hard to look at and
figure out what went wrong when things do go wrong.
I'd prefer something like:
https://gist.github.com/963027
But someone would have to
On 2011-05-09 19:58, Andrei Alexandrescu wrote:
On 5/9/11 12:24 PM, Jacob Carlborg wrote:
I
have a function that gets the path of the current process:
http://dsource.org/projects/tango/attachment/ticket/1536/process.d
This links to a file attached to a Tango ticket but don't worry, I've
writte
On 2011-05-09 20:03, Sean Kelly wrote:
On May 9, 2011, at 10:45 AM, Andrei Alexandrescu wrote:
On 5/9/11 12:24 PM, Jacob Carlborg wrote:
I assume the "initLogging" function needs the application command line
because you want to have the name of the application? If that's the
case, I don't like
On 09/05/2011 19:30, Robert Clipsham wrote:
The example looks great, exactly what I'd hope for in the way of a
logging library. A few questions:
* How do you disable logging at compile time? (and is it zero overhead?)
* How do you define your own logging backend?
* Is it possible to change loggi
On 09/05/2011 19:18, Andrej Mitrovic wrote:
I'm not a big fan of that format syntax. It's just hard to look at and
figure out what went wrong when things do go wrong.
I'd prefer something like:
https://gist.github.com/963027
But someone would have to implement it, of course. I have my own
littl
On 09/05/2011 07:52, Andrei Alexandrescu wrote:
On 5/7/11 3:43 PM, Jose Armando Garcia wrote:
Hey folks,
For the past couple of days I took the liberty of partially
implementing a logging module for D.
[snip]
Nice work. Also thanks for contacting me offline.
As I mentioned I'd already decide
On 2011-05-09 19:45, Andrei Alexandrescu wrote:
On 5/9/11 12:24 PM, Jacob Carlborg wrote:
I assume the "initLogging" function needs the application command line
because you want to have the name of the application? If that's the
case, I don't like that is handled via the application command line
On 2011-05-09 19:34, Andrei Alexandrescu wrote:
On 5/9/11 12:14 PM, Jacob Carlborg wrote:
On 2011-05-09 17:49, Andrei Alexandrescu wrote:
On 5/9/11 10:37 AM, Jacob Carlborg wrote:
Isn't the name of the log file a little too verbose? Don't know if I'm
missing something but this doesn't seem so
I'm not a big fan of that format syntax. It's just hard to look at and
figure out what went wrong when things do go wrong.
I'd prefer something like:
https://gist.github.com/963027
But someone would have to implement it, of course. I have my own
little echo() function which takes simple "{}" posi
On May 9, 2011, at 10:45 AM, Andrei Alexandrescu wrote:
> On 5/9/11 12:24 PM, Jacob Carlborg wrote:
>> I assume the "initLogging" function needs the application command line
>> because you want to have the name of the application? If that's the
>> case, I don't like that is handled via the applica
On 5/9/11 12:24 PM, Jacob Carlborg wrote:
I
have a function that gets the path of the current process:
http://dsource.org/projects/tango/attachment/ticket/1536/process.d
This links to a file attached to a Tango ticket but don't worry, I've
written the whole file myself and I intend to change th
On 5/9/11 12:24 PM, Jacob Carlborg wrote:
I assume the "initLogging" function needs the application command line
because you want to have the name of the application? If that's the
case, I don't like that is handled via the application command line. I
have a function that gets the path of the cur
On 5/9/11 12:14 PM, Jacob Carlborg wrote:
On 2011-05-09 17:49, Andrei Alexandrescu wrote:
On 5/9/11 10:37 AM, Jacob Carlborg wrote:
Isn't the name of the log file a little too verbose? Don't know if I'm
missing something but this doesn't seem so useful for long running
application that use logg
On 5/9/11 12:10 PM, Jacob Carlborg wrote:
On 2011-05-09 17:49, Andrei Alexandrescu wrote:
On 5/9/11 10:37 AM, Jacob Carlborg wrote:
Isn't the name of the log file a little too verbose? Don't know if I'm
missing something but this doesn't seem so useful for long running
application that use logg
On 2011-05-09 08:52, Andrei Alexandrescu wrote:
On 5/7/11 3:43 PM, Jose Armando Garcia wrote:
Hey folks,
For the past couple of days I took the liberty of partially
implementing a logging module for D.
[snip]
Nice work. Also thanks for contacting me offline.
As I mentioned I'd already decide
On 2011-05-09 17:49, Andrei Alexandrescu wrote:
On 5/9/11 10:37 AM, Jacob Carlborg wrote:
Isn't the name of the log file a little too verbose? Don't know if I'm
missing something but this doesn't seem so useful for long running
application that use logging. As far as I know you usually have one
On 2011-05-09 17:49, Andrei Alexandrescu wrote:
On 5/9/11 10:37 AM, Jacob Carlborg wrote:
Isn't the name of the log file a little too verbose? Don't know if I'm
missing something but this doesn't seem so useful for long running
application that use logging. As far as I know you usually have one
On 5/9/11 10:37 AM, Jacob Carlborg wrote:
Isn't the name of the log file a little too verbose? Don't know if I'm
missing something but this doesn't seem so useful for long running
application that use logging. As far as I know you usually have one log
file per application and outputs the message
On 2011-05-09 08:52, Andrei Alexandrescu wrote:
On 5/7/11 3:43 PM, Jose Armando Garcia wrote:
Hey folks,
For the past couple of days I took the liberty of partially
implementing a logging module for D.
[snip]
Nice work. Also thanks for contacting me offline.
As I mentioned I'd already decide
On 5/7/11 3:43 PM, Jose Armando Garcia wrote:
Hey folks,
For the past couple of days I took the liberty of partially
implementing a logging module for D.
[snip]
Nice work. Also thanks for contacting me offline.
As I mentioned I'd already decided I'll take a stab at implementing a
logging mod
On 2011-05-08 15:45, Michel Fortin wrote:
> On 2011-05-08 18:24:12 -0400, Jonathan M Davis said:
> >> On 5/8/2011 11:45 AM, Jose Armando Garcia wrote:
> >>> I am not sure I follow. Writing to disk is slower than writing to
> >>> memory so you want to hide some of the cost of logging by either
> >>
1 - 100 of 134 matches
Mail list logo