I second Rainer. A logging system should commit (at least) error messages
immediately, particularly if the application has multiple threads. Otherwise it
is going to make debugging a crashing system a nightmare. When I do it I just
stick 'synchronized' in front of the statement that does the
sybrandy Wrote:
> On 02/03/2010 12:03 AM, Rainer Deyke wrote:
> > sybrandy wrote:
> >> 1) I use the current core.thread library and put all my messages in a
> >> buffer that the thread checks periodically, pulls off a new message, and
> >> then writes it to a file. There will be some work to make
On 02/03/2010 12:03 AM, Rainer Deyke wrote:
sybrandy wrote:
1) I use the current core.thread library and put all my messages in a
buffer that the thread checks periodically, pulls off a new message, and
then writes it to a file. There will be some work to make sure nothing
collides with each ot
sybrandy wrote:
> 1) I use the current core.thread library and put all my messages in a
> buffer that the thread checks periodically, pulls off a new message, and
> then writes it to a file. There will be some work to make sure nothing
> collides with each other, but I think I can manage it.
Woul
Hello,
Since I'm continuing to write software in D (no, nothing special...just
pet projects) I felt that I needed to create a library to handle logging
to a file. I have a good start and it seems to work pretty well. I
even have a couple ideas left to implement to make it better, however
I'
