Re: OT: std.logger was Re: std.experimental Timeline

2016-01-05 Thread Robert burner Schadek via Digitalmars-d
On Tuesday, 5 January 2016 at 16:34:27 UTC, Dicebot wrote: BTW, the default implementation is a direct result of the "by default multi-threading safe" requirement brought up multiple times during reviews. .. this remains a concern. I know that with some tweaks and lot of custom overriding I

Re: OT: std.logger was Re: std.experimental Timeline

2016-01-05 Thread Dicebot via Digitalmars-d
Sorry for late reponse, I don't read NG that often now. On Monday, 4 January 2016 at 17:06:16 UTC, Robert burner Schadek wrote: I actually have a patch in the pipeline for this,. That patch require to change the protection for beginLogMsg, logMsgPart, finishLogMsg from protected to public and

Re: OT: std.logger was Re: std.experimental Timeline

2016-01-04 Thread Robert burner Schadek via Digitalmars-d
Yes the cast is ugly, but then I'm writing dynamic content into stack arrays. I actually have a patch in the pipeline for this,. That patch require to change the protection for beginLogMsg, logMsgPart, finishLogMsg from protected to public and bye bye cast. logMsgPart already takes a const(ch

Re: OT: std.logger was Re: std.experimental Timeline

2016-01-04 Thread Jonathan M Davis via Digitalmars-d
On Monday, 4 January 2016 at 13:48:16 UTC, Robert burner Schadek wrote: On Monday, 4 January 2016 at 10:58:09 UTC, Jonathan M Davis wrote: So, to work for them, they would need std.experimental.logger to accept something like const(char)[] or an arbitrary ranges of characters and to not allocat

Re: OT: std.logger was Re: std.experimental Timeline

2016-01-04 Thread Robert burner Schadek via Digitalmars-d
As talk is cheap, here is the code: http://dpaste.dzfl.pl/ba4df05339f6 not 20 lines but for 99 lines you get two Loggers and some tests.

Re: OT: std.logger was Re: std.experimental Timeline

2016-01-04 Thread Robert burner Schadek via Digitalmars-d
On Monday, 4 January 2016 at 10:58:09 UTC, Jonathan M Davis wrote: If I understand correctly (based on previous statements by Dicebot), the problem is that at Sociomantic, they reuse buffers heavily. So, they basically don't use string much of anywhere and instead use some combination of char[]

Re: OT: std.logger was Re: std.experimental Timeline

2016-01-04 Thread Jonathan M Davis via Digitalmars-d
On Monday, 4 January 2016 at 09:24:44 UTC, Robert burner Schadek wrote: On Sunday, 3 January 2016 at 21:37:28 UTC, Dicebot wrote: Haven't found any issues with std.allocator so far but std.logger definitely is not Phobos ready per my requirements. I have been recently re-evaluating it as possib

OT: std.logger was Re: std.experimental Timeline

2016-01-04 Thread Robert burner Schadek via Digitalmars-d
On Sunday, 3 January 2016 at 21:37:28 UTC, Dicebot wrote: Haven't found any issues with std.allocator so far but std.logger definitely is not Phobos ready per my requirements. I have been recently re-evaluating it as possible replacement for old Tango logger we use and found that in several pla