September 07, 2013
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
 * [new branch]      2.061      -> topull/2.061
 * [new branch]      bigintpure -> topull/bigintpure
 * [new branch]      candidate  -> topull/candidate
 * [new branch]      convpure   -> topull/convpure
 * [new branch]      deque      -> topull/deque
 * [new branch]      devel      -> topull/devel
 * [new branch]      gh-pages   -> topull/gh-pages
 * [new branch]      indexOfIdx -> topull/indexOfIdx
 * [new branch]      lastIndexOf -> topull/lastIndexOf
 * [new branch]      logger     -> topull/logger
 * [new branch]      master     -> topull/master
 * [new branch]      phobos-1.x -> topull/phobos-1.x
 * [new branch]      staging    -> topull/staging
 * [new branch]      website    -> topull/website

merging topull/logger
error: Your local changes to the following files would be overwritten by merge:
	win64.mak
Please, commit your changes or stash them before you can merge.
Aborting
Updating e723325..621af63


from the error message I would say somebody did modify the win64.mak on the test machine without committing it?


September 07, 2013
I would to drop some requirements I've seen in the Java world.

* As klamonte mention in the pull request on GitHub: Appenders are a must in a enterprise enviorment.
* Same with filters. In SLF4J normally each class has it's own logger which can be filtered or appended to individual files.
* Runtime configuration. Crucial when collection data about bugs in running systems.
* Performance... The possibility to write asynchronous loggers.
* Sometimes it's expensive to construct the log output. In Java for example Logback calls toString on objects after it has concluded that the data is needed. So a possibility to pass an function for constructing the log output only when the logger is sure that it's going to be logged.

My 2 SEK. ;-)
September 17, 2013
On Friday, 23 August 2013 at 20:11:38 UTC, H. S. Teoh wrote:
> On Fri, Aug 23, 2013 at 12:41:45PM -0700, 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 compile-time and
>> run-time configurability.
> [...]
>
> Where's the code?
>
>
> T

The code is here: https://github.com/jsancio/log.d/blob/master/src/log.d

For what it is worth, there was a lot of thought and effort that was put into the design, implementation and testing of it. If you are interested in the design goals of the std.log library then my recommendation is to learn about glog (http://google-glog.googlecode.com/svn/trunk/doc/glog.html). If the community decides that they like those design principles then I highly recommend you continue where std.log left off.

Thanks,
-Jose
1 2 3 4 5 6 7
Next ›   Last »