On 07/10/2014 10:31 PM, Walter Bright via Digitalmars-d wrote:
> On 7/10/2014 12:57 PM, Robert Schadek via Digitalmars-d wrote:
>> I know this is a bit OT and personal, but could somebody please merge
>> indexOfNeither aka indexOfNone. I just hate to copy this function from
>>
On 07/10/2014 06:05 PM, Sean Kelly via Digitalmars-d wrote:
> On Thursday, 10 July 2014 at 15:52:45 UTC, Andrei Alexandrescu wrote:
>> On 7/10/14, 8:29 AM, Sean Kelly wrote:
>>> Robert's struggle with getting std.logger accepted is the stuff told to
>>> children around the campfire so they don't ve
On 07/10/2014 05:59 PM, Dicebot via Digitalmars-d wrote:
> On Thursday, 10 July 2014 at 15:52:45 UTC, Andrei Alexandrescu wrote:
>> On 7/10/14, 8:29 AM, Sean Kelly wrote:
>>> Robert's struggle with getting std.logger accepted is the stuff told to
>>> children around the campfire so they don't ventu
On 07/05/2014 07:00 PM, Russel Winder via Digitalmars-d wrote:
> SCons 2.3.2 has been released which has the revamped D tooling.
>
> I appreciate Dub is becoming the build system of choice for new D
> projects, so I will maintain the D support in SCons but definitely in
> "maintenance mode" rather
On 06/30/2014 07:29 AM, Adam Wilson via Digitalmars-d wrote:
> On Sun, 29 Jun 2014 21:57:22 -0700, Suliman wrote:
>
>> Post screenshots please...
>
> Sadly I don't have anything that is visually beyond what I demoed at
> DConf so it's still just a blank window. I'm still down in the bowels
> of in
On 06/20/2014 02:56 PM, David Nadlinger via Digitalmars-d wrote:
> On Friday, 20 June 2014 at 12:34:55 UTC, Nick Treleaven wrote:
>> On 20/06/2014 13:32, Nick Treleaven wrote:
>>> It apparently shows the 3 main D compilers producing slower code than
>>> Go, Rust, gcc, clang, Nimrod:
>>
>> Also, it
On 06/20/2014 02:34 PM, Nick Treleaven via Digitalmars-d wrote:
> On 20/06/2014 13:32, Nick Treleaven wrote:
>> It apparently shows the 3 main D compilers producing slower code than
>> Go, Rust, gcc, clang, Nimrod:
>
> Also, it does appear to be using the correct compiler flags (at least
> for dmd)
On 06/13/2014 04:03 AM, Steven Schveighoffer via Digitalmars-d wrote:
> On Thu, 12 Jun 2014 21:22:25 -0400, Kapps wrote:
>
>> I could be wrong about this, but from what I remember this comes down
>> to DMC's runtime library. The max number of open file descriptors
>> with apis such as fopen is pre
Currently I have problems with my Logger PR. It magically fails from
time to time.
Whenever it fails std.socket fails with:
"Open file hard limit too low"
As far as I can see that is why my tests fail as well. Is this limit a
known problem? Suggestions?
On 06/06/2014 12:29 PM, Tom Browder via Digitalmars-d wrote:
> Can anyone point me to a text version of the D grammar in some kind of
> BNF or EBNF format? The D lang web site's info is close, but it's
> buried in html which I'ld rather not have to wrestle with.
>
> My purpose is to attempt to wri
On 05/30/2014 09:49 PM, Tobias Pankrath via Digitalmars-d wrote:
>> I know this is very early, but I work slowly :o)
>
> * Something like boost::log
phobos PR #1500 https://github.com/D-Programming-Language/phobos/pull/1500
> * Something like boost::program_options
phobos PR #2072 https://github.co
On 05/29/2014 12:41 PM, Jacob Carlborg via Digitalmars-d wrote:
> On 2014-05-29 12:09, Atila Neves wrote:
>
>> The GC is preventing me from beating Java, but not because of
>> collections. It's the locking it does to allocate instead! I
>> don't know about the rest of you but I definitely didn't se
On 05/07/2014 06:32 AM, Walter Bright via Digitalmars-d wrote:
>
> I had a car last year, and we stuffed it to the gills with people
> going between FB and Aloft. Will do so again this year.
>
I will have a car as well, but I'm staying on the other side of the bay.
I can take three people from FB t
On 03/17/2014 11:43 PM, Timon Gehr wrote:
> No, it does not. The lexer does not need to change.
you're right, but at some distant future I would like .. to be replaced
by :
On 03/17/2014 11:24 PM, H. S. Teoh wrote:
> On Mon, Mar 17, 2014 at 11:16:12PM +0100, Robert Schadek wrote:
>> replace .. with : to make lexing easier, please
> auto b = arr[(someCondition) ? w:x : y:z];
>
> :-(
>
>
> T
>
Thats a parsing problem.
1..1 makes y
replace .. with : to make lexing easier, please
On 03/12/2014 05:44 PM, Andrei Alexandrescu wrote:
> On 3/12/14, 4:08 AM, Iain Buclaw wrote:
>> Andrei, I'm looking at you.
>
> Hope not in a sexy way :o). I'm not sure that's a good idea - those
> are adult domains.
>
> Andrei
>
"bad publicity is better than none" at least we're not as uptight as
On 03/07/2014 12:56 PM, Vladimir Panteleev wrote:
> I'm glad I'm not the only one who feels this way. Implicit decoding
> must die.
>
> I strongly believe that implicit decoding of character points in
> std.range has been a mistake.
>
> - Algorithms such as "countUntil" will count code points. Thes
this one is just annoying, at least to me
https://d.puremagic.com/issues/show_bug.cgi?id=648
On 12/21/2013 10:43 PM, Andrej Mitrovic wrote:
> The compiler matches the missing symbol with the selective import
> "writeln", so it knows it only has to load std.stdio, *but not*
> std.algorithm.
>
> Test-case 3:
> -
> import std.stdio : writeln;
> import std.algorithm : map;
> import std.ran
On 12/04/2013 09:24 PM, Andrej Mitrovic wrote:
> On 11/1/13, Marenz wrote:
>> we at Sociomantic Labs are once again (or still) looking for
>> D-Developers in Berlin.
> Does that imply only people living near to Berlin should apply? If
> not, what does Sociomantic offer for people living abroad, e.
On 11/06/2013 02:21 PM, Dicebot wrote:
I see
On 11/05/2013 11:56 AM, t-dog wrote:
+1
On 11/04/2013 06:27 PM, Dicebot wrote:
> On Monday, 4 November 2013 at 17:08:21 UTC, Robert Schadek wrote:
>>> 4.
>>>
>>> Static "namespace" classes are redundant and should be replaced with
>>> module-scope globals.
>> not sure either
>
On 11/04/2013 02:46 PM, Dicebot wrote:
> On Monday, 14 October 2013 at 11:39:52 UTC, Dicebot wrote:
>> As `std.logger` is still marked as "work in progress" this thread is
>> less formal that typical pre-voting review. Goal is to provide as
>> much input about desirable `std.logger` functionality a
On 11/04/2013 06:52 AM, Philippe Sigaud wrote:
>
> On Mon, Nov 4, 2013 at 1:55 AM, Timothee Cour
> mailto:thelastmamm...@gmail.com>> wrote:
>
>
>> I guess I'll have to write a CT-compatible LALR(1) engine...
>>
> D does not fit into LALR(1), you need glr.
>
>
> Well, too b
On 11/04/2013 06:48 AM, Philippe Sigaud wrote:
> On Sun, Nov 3, 2013 at 7:08 PM, Timothee Cour
> mailto:thelastmamm...@gmail.com>> wrote:
>
>
> On Sun, Nov 3, 2013 at 1:13 AM, Philippe Sigaud
> mailto:philippe.sig...@gmail.com>>wrote:
>
>
> My current plan is to write different engi
On 11/03/2013 09:13 AM, Philippe Sigaud wrote:
>
> Oh, for D it works (it's even the biggest grammar I know), but it's
> too slow to be of practical interest. But that just means the
> generated parser is not top-notch, which is reasonable: I'm not a
> parsing pro, just a guy doing this during his
On 10/29/2013 11:02 AM, Dicebot wrote:
> On Tuesday, 29 October 2013 at 07:30:41 UTC, ilya-stromberg wrote:
>> It looks like we finished std.logger review.
>> Is it time to make some conclusion?
>
> Sorry, having lot of distraction lately. I am hoping to make a summary
> for std.logger and proceed
On 10/21/2013 10:19 PM, Dejan Lekic wrote:
> On Mon, 14 Oct 2013 13:39:51 +0200, Dicebot wrote:
>
>> As `std.logger` is still marked as "work in progress" this thread is
>> less formal that typical pre-voting review. Goal is to provide as much
>> input about desirable `std.logger` functionality and
On 10/21/2013 08:27 AM, SomeDude wrote:
>
> In practive, you really want a powerful logging facility.
> Another feature I used once in a project, was to log to RAM. We
> decided to log TRACE logs in production in order to catch a rare bug,
> but of course, it would output too many logs. So we decid
On 10/21/2013 06:19 AM, SomeDude wrote:
> On Tuesday, 15 October 2013 at 08:47:00 UTC, Robert Schadek wrote:
>> On 10/15/2013 09:32 AM, Sönke Ludwig wrote:
>>> Am 15.10.2013 09:08, schrieb Jacob Carlborg:
>>>> On 2013-10-14 23:22, Dicebot wrote:
>>>>
>
On 10/20/2013 08:52 AM, ilya-stromberg wrote:
> Also, Tango have log module:
> https://github.com/SiegeLord/Tango-D2/blob/d2port/tango/util/log/Log.d
I looked through the source and IMO the tango logger is my logger + (
configuration and more default logger) or the other way round. And this
thread
On 10/18/2013 03:49 PM, Dicebot wrote:
> On Friday, 18 October 2013 at 13:35:19 UTC, Robert Schadek wrote:
>> On 10/18/2013 02:55 PM, Dicebot wrote:
>>> Can you please re-generate the documentation after all recent updates?
>> I usually do that. The only documentation mi
On 10/18/2013 02:55 PM, Dicebot wrote:
> Can you please re-generate the documentation after all recent updates?
I usually do that. The only documentation missing is for MultiLogger, as
I'm not sure if the current implementation is done.
On 10/17/2013 04:13 AM, Eric Anderton wrote:
> On Tuesday, 15 October 2013 at 15:16:44 UTC, Andrei Alexandrescu wrote:
>> Eric, could you please enumerate a short list of features of log4j
>> that you think would be really missed if absent?
>
> Certainly. Here's my top 3, with some background to e
On 10/17/2013 09:34 AM, qznc wrote:
> On Thursday, 17 October 2013 at 02:13:12 UTC, Eric Anderton wrote:
>> The strength of this is that it would allow us to freely integrate D
>> libraries that use std.logger, yet filter their log output from
>> *outside* the library through the std.logger API.
>
; complications added as needed w/o code calling log() caring or changing.
>
>
> On Wed, Oct 16, 2013 at 12:30 AM, Robert Schadek <mailto:realbur...@gmx.de>> wrote:
>
> no hierarchical logs, KISS just create a logger with different
> destination. new FileLogger(&qu
On 10/16/2013 01:34 AM, Jeremy Powers wrote:
> On Tue, Oct 15, 2013 at 8:17 AM, Andrei Alexandrescu
> mailto:seewebsiteforem...@erdani.org>>
> wrote:
>
> One note - log4j, log4cxx, and log4cpp are not part of the
> respective languages' standards. That doesn't mean much (in fact
> it ma
On 10/15/2013 05:20 PM, Johannes Pfau wrote:
> I think one increasingly important point for std.log is 'structured
> logging'.
>
> Structured logging is basically not simply logging textual messages, but
> also logging additional KEY/VALUE pairs of data. The idea is that logs
> should not only be r
On 10/15/2013 04:23 PM, ilya-stromberg wrote:
> On Tuesday, 15 October 2013 at 14:20:15 UTC, Robert Schadek wrote:
>> Logging is the most unpure functionality I can think of. It is side
>> effect heaven.
>
> Yes, but we should minimise possible side effects.
Of course, but ha
On 10/15/2013 04:17 PM, ilya-stromberg wrote:
> On Tuesday, 15 October 2013 at 14:12:38 UTC, Sönke Ludwig wrote:
>> But if it's available people _will_ use it in complex contexts. Also
>> if the writer of a 2<<8 loc library uses it and the library is used
>> by a large piece of software, that will
On 10/15/2013 04:12 PM, Sönke Ludwig wrote:
>
> Believe it or not, for some reason I suspected as much.
>
> Yes, but the point is that when looking only at func1, you might
> expect that all messages are logged as debug messages, but the last
> one will be logged as a warning instead. func2 may be
On 10/15/2013 03:57 PM, Dicebot wrote:
> On Tuesday, 15 October 2013 at 13:52:17 UTC, Robert Schadek wrote:
>> I think this is good, as it gives you a way to quite libraries down. The
>> idea behind the free standing "log" function is to provide an ultra easy
>> wa
On 10/15/2013 03:54 PM, Dicebot wrote:
> On Tuesday, 15 October 2013 at 13:31:40 UTC, ilya-stromberg wrote:
>> ...
>
> I think such stuff should go as an extra module in same package with
> various useful out-of-the box logger implementations at the very best.
> Probably even dub package built on t
On 10/15/2013 03:31 PM, ilya-stromberg wrote:
> On Tuesday, 15 October 2013 at 07:52:28 UTC, Robert Schadek wrote:
>> On 10/15/2013 04:06 AM, Eric Anderton wrote:
>>> On Monday, 14 October 2013 at 11:39:52 UTC, Dicebot wrote:
>>> Here's what I think is missing:
>
On 10/15/2013 03:21 PM, Sönke Ludwig wrote:
> Am 15.10.2013 10:41, schrieb Robert Schadek:
>> On 10/15/2013 02:44 AM, Kapps wrote:
>>> The simple act of logging a message is very verbose right now:
>>> log(LogLevel.trace, "Creating new pool") is a lot of boiler
On 10/15/2013 02:54 PM, Sönke Ludwig wrote:
> What I meant is just that in Druntime there is something like this:
>
> struct LogManager {
> static void somefunc();
> }
>
> instead of
>
> class LogManager {
> static void someFunc();
> }
>
> In any case, such a struct/class should also have a mem
On 10/15/2013 10:49 AM, ponce wrote:
> What are the philosophy behind errors vs fatal errors vs critical errors?
> When should we use each of these?
fatal = the application is going down, I'm just letting you know
critical = the application is maybe going down, I'm not sure yet, but
this is a probl
On 10/15/2013 09:44 AM, ilya-stromberg wrote:
> On Monday, 14 October 2013 at 12:48:14 UTC, Martin Drasar wrote:
>> 1) MultiLogger class that takes references to other loggers and just
>> forwards the call to the log function.
>
> +1
> Also, we should support a few loggers whith same type. For exam
On 10/15/2013 09:40 AM, Sönke Ludwig wrote:
> Am 14.10.2013 20:24, schrieb Robert Schadek:
>> On 10/14/2013 04:44 PM, Sönke Ludwig wrote:
>>> The same could be said about the global "log" functions, which are
>>> tightly coupled to that state. I think this is a
On 10/15/2013 09:32 AM, Sönke Ludwig wrote:
> Am 15.10.2013 09:08, schrieb Jacob Carlborg:
>> On 2013-10-14 23:22, Dicebot wrote:
>>
>>> If we need to care about that, D module system is a failure.
>>> But I don't think it is a valid concern.
>>
>> People already complain about conflict function na
On 10/15/2013 02:44 AM, Kapps wrote:
> A few concerns:
>
> There doesn't seem to be a debug or trace log level. This is quite a
> useful thing to have once your program is deployed.
there is a LogLevel.debug and a LogLevel.info
>
> I don't like the returning by ref for log methods. For example, it
On 10/15/2013 04:06 AM, Eric Anderton wrote:
> On Monday, 14 October 2013 at 11:39:52 UTC, Dicebot wrote:
>> Lets unleash the forces of constructive destruction.
>
> So, not to be too heavy-handed with criticism on this library, but I
> think this should come up to par with solutions like log4j, lo
On 10/14/2013 11:10 PM, Guillaume Chatelet wrote:
>
> It is useful but it's also a pain to configure. I used logback (
> http://logback.qos.ch/ ) which is a bit nicer but still... We should
> definitely step away from XML's configuration mess.
Did somebody say XML, I first cast a stone. ;-) But ser
On 10/14/2013 07:01 PM, Jeremy Powers wrote:
> Some comments from the peanut gallery:
>
> * Mentioned already: configurable log output. Configure
> style/contents of log output based on output location. More options
> for included info (thread id, etc). Allow custom info to be inserted
> based o
On 10/14/2013 11:01 PM, Sean Kelly wrote:
> On Monday, 14 October 2013 at 20:49:19 UTC, Robert Schadek wrote:
>>
>> I disagree on having a simple email layer among the default logger,
>> because I feel that having this "special" logger in would water the
>>
On 10/14/2013 09:59 PM, ponce wrote:
> Thanks for taking care of that.
> My logger class logs warning in yellow and errors in red ;),
colors are awesome I now, but hard to do across all shells and even
worse when you want to pipe the messages in a file afterwards. So I
suggest you implement your ow
On 10/14/2013 08:55 PM, Sean Kelly wrote:
> It's weird that LogManager.defaultLogger exists as a read-only
> property, and if I want to change it I have to use the global static
> "log" variable.
this will be properly be fixed in the next incarnation (tonight, no
promises)
>
> I think this was ment
On 10/14/2013 08:29 PM, ilya-stromberg wrote:
>
> I said: "for example via `std.net.curl.SMTP`". If you don't want to
> use curl, you shouldn't. But yes, I think that e-mail logger can be
> useful. For example Linux use it (and bash can send errors via e-mail).
>
> About "email format config parser
On 10/14/2013 04:44 PM, Sönke Ludwig wrote:
> Am 14.10.2013 15:12, schrieb Robert Schadek:
>> On 10/14/2013 02:39 PM, Sönke Ludwig wrote:
>>> - The static methods in LogManager should be made global and the class
>>>be removed. It's not for objects so it sho
On 10/14/2013 05:27 PM, ilya-stromberg wrote:
>
> Add e-mail logger (useful for critical errors) for example via
> `std.net.curl.SMTP`.
And than at a email format config parser that fulfills everyones wishes,
would bet the idea of the design. And I though people where trying to
remove curl.
On 10/14/2013 03:31 PM, Martin Drasar wrote:
> On 14.10.2013 15:18, Robert Schadek wrote:
>> On 10/14/2013 02:32 PM, Martin Drasar wrote:
>>> 1) MultiLogger class that takes references to other loggers and just
>>> forwards the call to the log function.
>> will
On 10/14/2013 02:51 PM, Andrea Fontana wrote:
> Just for comparison, on Android you can write something like:
> FileLogger.w(...) instead of FileLogger.log(LogLevel.Warning...)
>
> (and there's a "wtf" loglevel for "temporary" debugging)
>
hm, I don't really like it. To me it sounds like, "I'm don
On 10/14/2013 02:32 PM, Martin Drasar wrote:
> Having skimmed through the docs I noticed that there are three features
> missing that I use and would like to see in standard logger. First is
> the ability to write to several loggers at once, the second is optional
> formatting of log output and the
On 10/14/2013 02:42 PM, Vladimir Panteleev wrote:
> Would be nice if either FileLogger, or a "proxy" logger available to
> users, would add timestamps. Timestamps are very useful for log files,
> as they allow to correlate logged events with other events on the
> system (e.g. other applications' lo
On 10/14/2013 02:39 PM, Sönke Ludwig wrote:
> Am 14.10.2013 13:39, schrieb Dicebot:
>> As `std.logger` is still marked as "work in progress" this thread is
>> less formal that typical pre-voting review. Goal is to provide as much
>> input about desirable `std.logger` functionality and current state
On 10/14/2013 12:28 PM, Abdulhaq wrote:
>
>
> Also, does SMOKE do anything for you in terms of signals and slots,
> and QVariants?
Signal and Slots are sort of replaced by "normal" methods and a
different connect function in Qt5, which is awesome, because you will
get compile time errors instead of
On 10/10/2013 03:45 AM, Walter Bright wrote:
> Rainer Schuetze wrote:
>
> You have to put the lock around the pair of AddRef and Release, but if
> the compiler already splits this into two function calls, this cannot
> be done in the implementation.
I would imagine the counter to be manipulated wit
On 10/10/2013 09:33 AM, Jonathan M Davis wrote:
> I honestly don't think we can solve it a different way without completely
> redesigning shared. shared is specifically designed such that you have to
> either cast it way to do anything with it or write all of your code to
> explicitly work with
On 10/09/2013 04:22 AM, Andrei Alexandrescu wrote:
>
> * Get Robert Schadek's precise GC in. Walter and I have become 101%
> convinced a precise GC is the one way to go about GC.
>
I would like to claim that work, but the Rainer Schütze wrote that. I
know, both german, same initials.
On 10/04/2013 12:02 PM, John Colvin wrote:
> Adding new (or replacement) phobos modules without wider testing is
> not a scalable approach for D.
> New modules go from unofficial to official in a single step and are
> therefore inadequately battle-tested before becoming part of the
> somewhat ossif
On 10/04/2013 04:36 AM, David Nadlinger wrote:
> Maybe you can elaborate a bit on how the problem occurs in that
> context? As I said, I've found that usually it is possible to come up
> with a design at least as pretty (or even prettier) but doesn't rely
> on stringof trickery if one just stares a
On 10/04/2013 09:07 AM, Dicebot wrote:
> P.S. I have tried contacting you in context of std.logger, is mail
> address mentioned on github valid one? If not, please ping me via
> public.dicebot.lv
Yes it is, strange. Try the one I use here.
On 10/03/2013 08:10 PM, David Nadlinger wrote:
> On Thursday, 3 October 2013 at 17:52:13 UTC, Robert Schadek wrote:
>>
>> dmd moduleA.d moduleB.d -ofmix -unittest
>> moduleA.d(4): Error: undefined identifier Foo
>> moduleB.d(10): Error: template instance A.func!(Foo)
I have some found some irregular behavior when using mixins with
template and modules. If a aggregation is defined in the same module it
is found. If the aggregation is defined in another module it fails. And
I wonder if this is be design. For comparison see the code below.
// file: moduleA.d
mod
On 09/23/2013 09:11 PM, Andrei Alexandrescu wrote:
> On 9/23/13 11:55 AM, Robert Schadek wrote:
>> On 09/23/2013 07:16 PM, Andrei Alexandrescu wrote:
>>> On 9/23/13 10:01 AM, deadalnix wrote:
>>>
>>>> Finally, we got to decide how these basics block are used
On 09/23/2013 07:16 PM, Andrei Alexandrescu wrote:
> On 9/23/13 10:01 AM, deadalnix wrote:
>
>> Finally, we got to decide how these basics block are used to form typed
>> allocators, and interact with language constructs.
>
> Sure. Again: I describe the Otto cycle and you discuss how to paint
> the
On 09/12/2013 11:03 PM, Dmitry Olshansky wrote:
>> Maybe some fixed size stack vector with 64 elements or so and some
>> linked list for the unusual case would help ..
>>
> And an extra branch to detect which one is currently the case? No,
> thanks ;)
>
I would think that branching and using the ve
On 09/12/2013 04:21 AM, Martin Nowak wrote:
> On 09/12/2013 03:39 AM, Walter Bright wrote:
>> On 9/11/2013 6:30 PM, deadalnix wrote:
>>> Indeed. What solution do you have in mind ?
>>
>> The solution dmd uses is to put in an intermediary layer that saves the
>> lookahead tokens in a linked list.
>
On 09/12/2013 12:09 AM, Manfred Nowak wrote:
> Walter Bright wrote:
>
>> Since the very beginning.
>>
>> One example is determining if something is a declaration or an
>> expression.
> I see now, that you wrote about parsing---not about lexing.
>
> Btw. I wrote an LALR(1)-parser for an early versi
On 09/10/2013 03:45 PM, Dicebot wrote:
>
>> done and done (the design of my logger is based on what I distilled from
>> the old discussion)
>
> Thanks! You will be next after Brian then (pardon me for wanting
> std.d.lexer so much :P)
No problem, it might be good though to get so bashing beforehand
On 09/10/2013 01:43 PM, Dicebot wrote:
> You should add it to http://wiki.dlang.org/Review_Queue then, there is
> also a link to an old review thread of `std.log` by Jose Armando
> Garcia which may be of interest to you as people are likely to ask
> similar questions :)
done and done (the design of
On 09/09/2013 04:21 PM, Dicebot wrote:
> While Jacob is working on improving std.serialization, there is some
> time to do more reviews. Review manager role does not seem to be very
> stressing, so I can step up as one for any of the projects currently
> in queue as soon as their authors express th
On 09/08/2013 06:46 AM, Jonathan M Davis wrote:
> If I had to vote though, I'd vote against this, because I think that
> it's a bad paradigm, and I don't want to deal with it.
+1
Most awesome
On 08/22/2013 05:06 PM, Johannes Pfau wrote:
I'm getting wired auto-tester erros
setting up remote topull -> https://github.com/burner/phobos.git
fetching contents of https://github.com/burner/phobos.git
>From https://github.com/burner/phobos
* [new branch] 10472 -> topull/10472
* [n
On 09/02/2013 11:55 AM, deadalnix wrote:
>
> I don't think that githubing everything is a wise move.
ok, why do you think that?
On 09/01/2013 08:43 PM, Andrej Mitrovic wrote:
> On 9/1/13, Manu wrote:
>> None of the others could be bothered creating yet-another-webpage-account to
>> log bugs
>> they encountered. I suggested they do so a few times. I was promptly ignored.
>> It's just that manually logging in to non-ajax we
On 08/29/2013 11:09 AM, Jacob Carlborg wrote:
>
> So you want serialization :). Which we currently are reviewing.
> Unfortunately there might be too many changes needed to get it in
> Phobos this time.
>
well, sort of, but also with partial serialization (think sql update),
more transparent interfa
On 08/29/2013 09:51 AM, Johannes Pfau wrote:
> I most points here also apply to std.xml:
> http://wiki.dlang.org/Wish_list/std.json Those are not strict
> requirements though, I just summarized what I remembered from old
> discussions.
I think, this even extends to access to all semi- and structure
On 08/24/2013 08:01 PM, Jonathan M Davis wrote:
> On Saturday, August 24, 2013 16:49:24 SomeDude wrote:
>> OTOH, they are used in just about every logging API ever devised.
>> Everybody knows what they mean. I just don't see the need to
>> reinvent these words and make them longer by adding log. I
On 08/23/2013 11:49 PM, Andrei Alexandrescu wrote:
> On 8/23/13 1:10 PM, Robert Schadek wrote:
>> On 08/23/2013 09:41 PM, Andrei Alexandrescu wrote:
>>> (Just hanging this to a random comment in this thread.) I think
>>> there's some pretty good work on logg
On 08/23/2013 10:08 PM, Jonathan M Davis wrote:
> On Friday, August 23, 2013 21:47:44 Johannes Pfau wrote:
>
>> Make the templated function a stub which redirects to a function which
>> uses normal function arguments and rely on inlining?
> Inlining will have no effect on __FILE__ and __LINE__, and
On 08/23/2013 10:34 PM, Jacob Carlborg wrote:
> On 2013-08-23 18:48, Robert Schadek wrote:
>
>> I do as well, but this will lead to template bloat, as many people will
>> tell you, and log("device id: %s".format(device.id)); is
>> not so bad.
>
> Won&#
On 08/23/2013 09:41 PM, Andrei Alexandrescu wrote:
> (Just hanging this to a random comment in this thread.) I think
> there's some pretty good work on logging by myself and another poster
> (Jose?) that has since gone abandoned. It included some nice approach
> to conditional logging and had both
On 08/23/2013 07:21 PM, Gary Willoughby wrote:
> I don't think you can bloat a simple logger too much with templates.
> It's a pretty simple framework.
every log call with more than a string will be a template. My first
private logger version was like this.
After reading the last logger thread and
On 08/23/2013 06:28 PM, Gary Willoughby wrote:
> On Thursday, 22 August 2013 at 14:13:29 UTC, Robert Schadek wrote:
>> lots..
>
> Just to weight in and give my four penneth. It needs to be made a
> little more flexible in the formats it produces (syslog?) and the
> input it
On 08/23/2013 02:56 PM, Piotr Szturmaj wrote:
> W dniu 23.08.2013 14:16, Robert Schadek pisze:
>> On 08/23/2013 01:10 PM, Piotr Szturmaj wrote:
>>> so if I have a LogLevel variable I want to use:
>>>
>>> LogLevel myLogLevel;
>>>
>>> I need to
On 08/23/2013 01:10 PM, Piotr Szturmaj wrote:
> so if I have a LogLevel variable I want to use:
>
> LogLevel myLogLevel;
>
> I need to write this:
>
> # alternative 1 (possibly wrapped in a function)
> switch (myLogLevel)
> {
> case LogLevel.Info: log.Info("..."); break;
> case LogLevel.War
1 - 100 of 127 matches
Mail list logo
