On Wednesday, 14 August 2013 at 16:25:21 UTC, Andrei Alexandrescu
wrote:
On 8/14/13 1:48 AM, Jacob Carlborg wrote:
On 2013-08-14 10:19, Tyler Jameson Little wrote:
- I would to serialize to a range (file?) and deserialize
from a
range (file?)
The serialized data is returned as an array, so
Hi,
Do you know any cryptographically secure pseudo-random number
generator (CSPRNG) for D?
I know that we have std.random, but it is NOT cryptographically
secure.
Thanks.
On Sunday, 18 August 2013 at 18:26:55 UTC, Dicebot wrote:
On Monday, 12 August 2013 at 13:27:45 UTC, Dicebot wrote:
Stepping up to act as a Review Manager for Jacob Carlborg
std.serialization
So as a review manager, I think voting should be delayed until
API is ready to address lazy range-bas
On Monday, 19 August 2013 at 12:49:48 UTC, Jacob Carlborg wrote:
I have had a brief look at Protocol Buffers and I don't see why
it wouldn't work as an archive. I would probably need to
implement a Protocol Buffers archive type to see what the
limitations of std.serialization and Protocol Buffe
On Thursday, 15 August 2013 at 20:12:44 UTC, Jacob Carlborg wrote:
I just noticed that ClassInfo.find not working for nested
classes, even if they are static. For example:
Bugzilla?
On Sunday, 18 August 2013 at 19:32:50 UTC, QAston wrote:
You may be interested in
https://github.com/D-Programming-Deimos/openssl - D bindings
for openssl.
How can I get access to the /dev/random or /dev/urandom (Linux
only)? Like a file via std.file, or D have spesial function?
On Tuesday, 20 August 2013 at 03:42:48 UTC, Tyler Jameson Little
wrote:
On Monday, 19 August 2013 at 18:06:00 UTC, Johannes Pfau wrote:
An important question regarding ranges for std.serialization
is whether
we want it to work as an InputRange or if it should _take_ an
OutputRange. So the quest
On Tuesday, 20 August 2013 at 10:51:25 UTC, Johannes Pfau wrote:
Am Tue, 20 Aug 2013 10:40:57 +0200
schrieb "ilya-stromberg" :
We can use InputRange like this:
import std.file;
auto archive = new Archive()
Serializer(archive).serialize(object);
//Archive implements InputRange for uby
On Tuesday, 20 August 2013 at 15:07:39 UTC, Tyler Jameson Little
wrote:
On Tuesday, 20 August 2013 at 13:44:01 UTC, Daniel Murphy wrote:
"Dicebot" wrote in message
news:luhuyerzmkebcltxh...@forum.dlang.org...
What I really don't like is excessive amount of object in the
API. For example, I h
On Wednesday, 21 August 2013 at 06:55:56 UTC, Jacob Carlborg
wrote:
On 2013-08-21 02:09, Dicebot wrote:
P.S. Right now most important (and probably only really
important) thing
is range API. I think it is worth focusing on it and getting
through the
voting stage - actual merge can happen at any
On Sunday, 18 August 2013 at 19:46:00 UTC, Jacob Carlborg wrote:
If versioning is crucial it can be added.
Can std.serialization load data if class definition was changed?
For example, we have class "Foo":
class Foo
{
int a;
int b;
}
and we serialize it in some file. After that class
On Thursday, 22 August 2013 at 17:09:17 UTC, Robert Schadek wrote:
On 08/22/2013 05:59 PM, Jacob Carlborg wrote:
But still, I like that very much, even though this is still in
conflict
with std.math.log.
We should avoid name conflicts as much as possible. So, I vote to
the Craig Dillabaugh's i
On Thursday, 22 August 2013 at 13:13:48 UTC, Jacob Carlborg wrote:
On 2013-08-22 13:57, ilya-stromberg wrote:
Can std.serialization load data if class definition was
changed?
Yes. In this case it will use the name of the instance fields
when searching for values in the archive.
Great! What
On Thursday, 22 August 2013 at 19:53:53 UTC, Jacob Carlborg wrote:
On 2013-08-22 21:30, ilya-stromberg wrote:
What about more difficult cases?
No it can't. It will throw an exception because it cannot find
a "long" element:
Could not find an element "long" with
On Friday, 23 August 2013 at 20:28:10 UTC, Jacob Carlborg wrote:
On 2013-08-22 21:30, ilya-stromberg wrote:
What about more difficult cases?
Actually, my previous answer was not entirely correct. By
default it will throw an exception. But you can implement the
above using custom
On Thursday, 22 August 2013 at 15:15:37 UTC, Johannes Pfau wrote:
Am Tue, 06 Aug 2013 23:28:51 +0200
schrieb "Timofei Bolshakov" :
I was trying to compile the latest version of GDC for ARM and
meet multiple problems with static asserts. Do you know if ARM
fixes exists?
Sorry for the late ans
On Saturday, 24 August 2013 at 17:47:35 UTC, Jacob Carlborg wrote:
I actually noticed this problem when I wrote the example.
First, the interface Serializable is actually not necessary
because this is actually checked with at template at compile
time, it's possible to use these methods for stru
On Saturday, 24 August 2013 at 19:32:13 UTC, Jacob Carlborg wrote:
On 2013-08-24 21:26, ilya-stromberg wrote:
In that case maybe we should remove "Serializable" interface?
And just
spesify that user must implement "toData" or "fromData" for
custom
serializing or
On Saturday, 24 August 2013 at 18:00:05 UTC, Johannes Pfau wrote:
Am Sat, 24 Aug 2013 19:18:42 +0200
schrieb "ilya-stromberg" :
Do you have any plans for Android support?
Not until the 'usual' Linux/GlibC combination works well on ARM.
I understood. How are you close to
On Saturday, 24 August 2013 at 10:24:33 UTC, Jason den Dulk wrote:
You can get it at
http://jaypha.com.au/fcgi.zip
I don't have a github account as yet, but I will get one if
people like my code enough.
Please, put the code to github. It's easy.
On Saturday, 24 August 2013 at 17:47:35 UTC, Jacob Carlborg wrote:
First, the interface Serializable is actually not necessary
because this is actually checked with at template at compile
time, it's possible to use these methods for structs as well.
Second, instead of checking for both "toData"
On Friday, 23 August 2013 at 13:39:47 UTC, Dicebot wrote:
On Friday, 23 August 2013 at 13:34:04 UTC, ilya-stromberg wrote:
It's a serious issue. May be it's more important than range
support. For example, I have to change class (bug fixing, new
features, etc.), but it comparable wi
On Wednesday, 28 August 2013 at 16:10:03 UTC, Dicebot wrote:
There was a good proposal by Dmitry to separate sequential
strict serialization for random-access one as two distinct
entities. I like it and I think it that is also can solve your
problem.
The problem is not only my. Actually, I di
Hi.
Do you know any library with high-precision doubles? I need at
least 20-30 decimal digits without rounding, it will be better to
have 50-100 decimal digits.
Thanks.
On Thursday, 29 August 2013 at 13:37:47 UTC, Craig Dillabaugh
wrote:
This isn't a D library, but GMP might fit your needs:
http://gmplib.org/
It is in C, so you should be able to interface with D code.
Craig
Thanks.
Anybody knows a D interface for the GMP library? I can't find it
at the De
On Thursday, 29 August 2013 at 13:53:42 UTC, qznc wrote:
Phobos has std.bigint, but the documentation recommends GMP for
"very large numbers".
http://dlang.org/phobos/std_bigint.html
No, I need double, not integer, so I can't use std.bigint.
I must provide at least 20-30 decimal digits withou
D can not override template and nontemplate function:
void foo(bool param)
{
if(param)
{
//do something useful
}
else
{
//do something else
}
}
void foo(bool param)()
{
static if(param)
{
On Saturday, 31 August 2013 at 12:19:17 UTC, monarch_dodra wrote:
While we are at it, this is also the way to "force" attribute
inference on a function.
Can you print any code example, please?
On Thursday, 29 August 2013 at 07:53:46 UTC, Tobias Pankrath
wrote:
There is http://dsource.org/projects/xmlp, which at some point
has been proposed for std.xml2. But that stalled for some time
now.
Also, we have Tango Xml:
https://github.com/SiegeLord/Tango-D2/tree/d2port/tango/text/xml
It's
On Saturday, 31 August 2013 at 18:03:10 UTC, Jacob Carlborg wrote:
Unfortunately the Tango XML package will never end up in Phobos
due to licensing issues.
Yes, but we can always learn source code and put attention to the
design solutions.
On Thursday, 22 August 2013 at 19:53:53 UTC, Jacob Carlborg wrote:
On 2013-08-22 21:30, ilya-stromberg wrote:
Great! What about more difficult cases? For example, we have:
class Foo
{
int a;
int b;
}
After changes we have new class:
class Foo
{
long b;
}
Can std.serialization load
On Sunday, 1 September 2013 at 08:33:51 UTC, ilya-stromberg wrote:
On Thursday, 22 August 2013 at 19:53:53 UTC, Jacob Carlborg
wrote:
On 2013-08-22 21:30, ilya-stromberg wrote:
Great! What about more difficult cases? For example, we have:
class Foo
{
int a;
int b;
}
After changes we
On Thursday, 29 August 2013 at 16:14:28 UTC, Michel Fortin wrote:
I wrote something like that a while ago.
It only accepted arrays as input because of the lack of a
"buffered range" concept that'd allow lookahead and efficient
slicing from any kind of range, but that could be retrofitted
in.
On Wednesday, 14 August 2013 at 09:26:55 UTC, Jacob Carlborg
wrote:
On 2013-08-14 11:17, Tove wrote:
I find the newstyle both more intuitive and you also more dry
not
duplicating the identifier: "int b; mixin NonSerialized!(b)"
@nonSerialized struct Foo
{
int a;
int b;
int c;
}
st
Do you have any plans to support implicit conversion between
types?
I have some code like this:
struct Foo
{
this(int i)
{
//do something useful
}
}
void bar(Foo f)
{
//do something else
}
void main()
{
Foo f = 5;//works
On Friday, 6 September 2013 at 11:32:11 UTC, Benjamin Thaut wrote:
Am 06.09.2013 13:27, schrieb Dicebot:
On Friday, 6 September 2013 at 11:04:31 UTC, Peter Alexander
wrote:
Implicit conversions open up a whole can of worms for the
sake of a
small amount of convenience.
I'm not sure it's a fai
On Friday, 6 September 2013 at 13:01:14 UTC, Dicebot wrote:
For example, use case that justifies operator overloading
(despite the danger) in my eyes is ability to replace built-in
types with custom ones. What is the similar rationale for
implicit conversion?
For exaple, for generic code:
T
On Friday, 6 September 2013 at 13:25:37 UTC, Flamaros wrote:
It's difficult to never forget the "explicit" keyword in c++,
and this little mistake can make you loose a lot of time.
I prefer to only have explicit conversions with cast or
constructors calls, that all make the code easier to unde
On Friday, 6 September 2013 at 13:30:26 UTC, Dicebot wrote:
So, what essentially is needed, is ability to implicitly
convert literals of built-in types to user types, not any
possible implicit conversion?
I think allowing it with such restrictions can be reasonably
clean.
Yes, the ability t
On Friday, 6 September 2013 at 13:39:20 UTC, deadalnix wrote:
You don't want a keyword for that. Something obscure and ugly
is required.
C# have operator overloading for this.
We can use, for example, "opImplicitRightCast"
struct Foo
{
Foo opImplicitRightCast(T)(T from);
}
On Friday, 6 September 2013 at 14:26:17 UTC, H. S. Teoh wrote:
I thought the usual D idiom was to write factorial(5) and
factorial(BigInt(5)) and let the compiler figure out which
template
instance you wanted?
Yes, but it isn't always possible.
It can be critical for more complex cases, when
On Friday, 6 September 2013 at 17:15:03 UTC, H. S. Teoh wrote:
Hmm, could this be a possible (though somewhat ugly) workaround?
foreach (T; IntegralTypeList)
{
assert(factorial(to!T(3) == 6));
}
AFAIK, if T==int, then std.conv.to should simply alias itsel
On Friday, 6 September 2013 at 15:47:27 UTC, Dicebot wrote:
On Friday, 6 September 2013 at 15:14:50 UTC, ilya-stromberg
wrote:
As monarch_dodra pointed above, we haven't got "uniform
construction" support.
Yeah, this one, contrary, seems to be really crucial feature
lacking.
On Friday, 6 September 2013 at 13:01:14 UTC, Dicebot wrote:
On Friday, 6 September 2013 at 11:32:11 UTC, Benjamin Thaut
wrote:
Its only a source of troubles in C++ because it is the default
behavior. But if you design a library it can make the usage of
your api easier and also you have a few mo
On Saturday, 7 September 2013 at 13:02:39 UTC, Simen Kjaeraas
wrote:
It's a bit weird in D though, as operators are instance
methods, and
opImplicitRightCast (or opImplicitCastFrom, which is the name
used in
discussions before, see WalterAndrei.pdf from back when
dinosaurs roamed the
earth) sho
On Wednesday, 11 September 2013 at 06:28:30 UTC, Sönke Ludwig
wrote:
Am 11.09.2013 00:06, schrieb luminousone:
Projects that haven't had an update for an excessive amount of
time should likely be hidden but still available except in
cases
where it is known to be unchanged without need for upda
On Wednesday, 11 September 2013 at 11:31:11 UTC, Faux Amis wrote:
On 11-9-2013 12:28, ilya-stromberg wrote:
On Wednesday, 11 September 2013 at 06:28:30 UTC, Sönke Ludwig
wrote:
Am 11.09.2013 00:06, schrieb luminousone:
Projects that haven't had an update for an excessive amount
of
time s
On Monday, 9 September 2013 at 14:21:17 UTC, 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 a
On Wednesday, 4 September 2013 at 07:04:01 UTC, Elvis wrote:
I'm new to D, from what I read in Reddit these days, it's
really really bad that D's supporter always claim that D
support Manual Memory Management and GC can be disabled ,
despite the truth that druntime/phobos are parts of D to an e
On Sunday, 15 September 2013 at 18:28:25 UTC, Dicebot wrote:
On Saturday, 14 September 2013 at 12:19:18 UTC, ilya-stromberg
wrote:
On Wednesday, 4 September 2013 at 07:04:01 UTC, Elvis wrote:
I'm new to D, from what I read in Reddit these days, it's
really really bad that D's s
I asked about a library with high-precision doubles 3 weeks ago.
Now I find std.decimal module at the Review Queue page:
https://github.com/andersonpd/decimal
The author is Paul D. Anderson. Last commit was 4 months ago.
It's interesting to know a current project state.
On Wednesday, 11 September 2013 at 15:02:00 UTC, Dicebot wrote:
std.d.lexer is standard module for lexing D code, written by
Brian Schott
Brian, have you got any plans to write common lexer/parser
generator based on context-free grammar (CFG) or parsing
expression grammar (PEG), not only for
On Wednesday, 11 September 2013 at 09:14:59 UTC, Robert Schadek
wrote:
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 :
On Monday, 30 September 2013 at 18:01:29 UTC, Joseph Rushton
Wakeling wrote:
On 30/09/13 19:39, Joseph Rushton Wakeling wrote:
... although the new gcf will fail if passed immutable/const
BigInts.
On this note:
http://d.puremagic.com/issues/show_bug.cgi?id=11148
I had to tweak CommonInteger
On Monday, 30 September 2013 at 18:14:13 UTC, simendsjo wrote:
On Monday, 30 September 2013 at 16:27:16 UTC, Brad Anderson
wrote:
On Saturday, 28 September 2013 at 16:39:27 UTC, simendsjo
wrote:
I've been working on a more or less complete rewrite of the
mysql-native module.
I don't have any
On Tuesday, 1 October 2013 at 08:02:12 UTC, Joseph Rushton
Wakeling wrote:
On 01/10/13 08:26, ilya-stromberg wrote:
Note that denumerator must be allways positive (> 0).
But numerator can be positive, zero or negative, and can be
bigger than
denumerator.
It means that we can use differ
On Sunday, 29 September 2013 at 15:11:26 UTC, Dicebot wrote:
On Sunday, 29 September 2013 at 14:58:17 UTC, ilya-stromberg
wrote:
It looks like we finished review of std.d.lexer.
Do you have any plans to start review for Robert Schadek's
std.logger?
Brian has made several quick
On Wednesday, 2 October 2013 at 15:46:06 UTC, Jesse Phillips
wrote:
On Wednesday, 2 October 2013 at 15:07:43 UTC, ilya-stromberg
wrote:
On Sunday, 29 September 2013 at 15:11:26 UTC, Dicebot wrote:
On Sunday, 29 September 2013 at 14:58:17 UTC, ilya-stromberg
wrote:
It looks like we finished
On Thursday, 3 October 2013 at 14:23:42 UTC, Dicebot wrote:
On Thursday, 3 October 2013 at 14:13:58 UTC, ilya-stromberg
wrote:
What happens if I vote "Yes with condition", but module
developer will not satisfy the condition? My vote will be
calculated as "No", as "Yes
On Wednesday, 2 October 2013 at 14:41:56 UTC, Dicebot wrote:
After brief discussion with Brian and gathering data from the
review thread, I have decided to start voting for `std.d.lexer`
inclusion into Phobos.
No.
I really want to see `std.d.lexer` in Phobos, but have too many
conditions.
On Friday, 4 October 2013 at 14:30:12 UTC, Craig Dillabaugh wrote:
On Friday, 4 October 2013 at 09:41:49 UTC, ilya-stromberg wrote:
On Wednesday, 2 October 2013 at 14:41:56 UTC, Dicebot wrote:
After brief discussion with Brian and gathering data from the
review thread, I have decided to start
On Friday, 27 September 2013 at 10:57:50 UTC, Dicebot wrote:
I have been looking at http://wiki.dlang.org/Review_Queue and
it feels like it lacks some short summary for projects - only
voting results and raw links to threads are presented here.
Probably it would have made sense to have a separa
On Saturday, 5 October 2013 at 11:45:47 UTC, Jacob Carlborg wrote:
On 2013-10-05 02:24, Andrei Alexandrescu wrote:
Thanks all involved for the work, first of all Brian.
I have the proverbial good news and bad news. The only bad
news is that
I'm voting "no" on this proposal.
[Snip]
Is this
On Sunday, 6 October 2013 at 08:59:57 UTC, Jacob Carlborg wrote:
I just think that if you were not completely satisfied with the
current API or implementation you could have said so in the
discussion thread. It would have at least given Brian a chance
to do something about it, before the voting
On Sunday, 6 October 2013 at 18:54:55 UTC, Dicebot wrote:
Any formal review may potentially result in short voting after
if no critical issues are found so I don't think it makes sense
in making any additional announcements. There are no special
points of attention - if review was declared and
On Tuesday, 8 October 2013 at 00:16:45 UTC, Andrei Alexandrescu
wrote:
To put my money where my mouth is, I have a proof-of-concept
tokenizer for C++ in working state.
http://dpaste.dzfl.pl/d07dd46d
Why do you use "\0" as end-of-stream token:
/**
* All token types include regular and re
On Wednesday, 9 October 2013 at 07:49:55 UTC, Andrei Alexandrescu
wrote:
On 10/8/13 11:11 PM, ilya-stromberg wrote:
On Tuesday, 8 October 2013 at 00:16:45 UTC, Andrei
Alexandrescu wrote:
To put my money where my mouth is, I have a proof-of-concept
tokenizer
for C++ in working state.
http
On Thursday, 10 October 2013 at 03:14:30 UTC, Jesse Phillips
wrote:
There is little documentation on how to handle the situation
the Review Manager is currently facing. I would like to open
this discussion to point out why, and to poll for if we should
have any.
The reason is that our process
On Monday, 9 September 2013 at 14:21:17 UTC, 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 a
On Sunday, 13 October 2013 at 12:36:20 UTC, nickles wrote:
Why does .length return the number of bytes and not the
number of UTF-8 characters, whereas length and
.length return the number of UTF-16 and UTF-32
characters?
Wouldn't it be more consistent to have .length return
the
number of UTF-8
On Saturday, 12 October 2013 at 19:25:01 UTC, Robert wrote:
Do you have any plans to include the code into Phobos?
Of course! :-) I am just waiting until people have finished
reviewing all the other good stuff and a review manager is
needed indeed. It might not be a bad idea to pick it up ne
On Sunday, 13 October 2013 at 07:47:55 UTC, Denis Shelomovskij
wrote:
--- Proposal ---
The proposal is to add weak reference functionality based on
`unstd.memory.weakref`. It can be placed e.g. in `core.memory`.
+1
On Tuesday, 8 October 2013 at 14:41:47 UTC, Denis Shelomovskij
wrote:
I accidentally discovered Andrei wrote [1] multidimensional
array implementation is needed. If it really is, I will work to
revise the API and prepare my implementation [2] for review if
nobody is doing it already.
Also as
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 and current state and let module author to use
On Monday, 14 October 2013 at 13:39:10 UTC, Byron wrote:
** System logging: syslog and windows event logging support.
+1, add System logging, and use as default windows event logging
for windows and syslog for POSIX.
And remote log support for syslog to allow send log messages via
network.
On Monday, 14 October 2013 at 18:00:12 UTC, Robert Schadek wrote:
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
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
example, I can use 2 file loggers: the 1-st only for debug
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:
- System log support (as others have mentioned). This would
be syslog
or WEL, depending on
On Tuesday, 15 October 2013 at 13:54:12 UTC, 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
On Tuesday, 15 October 2013 at 14:12:38 UTC, Sönke Ludwig wrote:
Am 15.10.2013 15:52, schrieb Robert Schadek:
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
On Tuesday, 15 October 2013 at 14:20:15 UTC, Robert Schadek wrote:
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 th
On Tuesday, 15 October 2013 at 14:13:53 UTC, Dicebot wrote:
On Tuesday, 15 October 2013 at 14:09:36 UTC, ilya-stromberg
wrote:
I did not talk about additional external libraries. As I know,
Vibe.d use OpenSSL to provide SSL streams. Since we haven't
got encryption support in Phobos, w
On Tuesday, 15 October 2013 at 14:25:55 UTC, Robert Schadek wrote:
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
On Tuesday, 15 October 2013 at 07:52:28 UTC, Robert Schadek wrote:
On 10/15/2013 04:06 AM, Eric Anderton wrote:
Here's what I think is missing:
- System log support (as others have mentioned). This would
be syslog
or WEL, depending on environment.
This is sort of the idea of the design, I can
On Tuesday, 15 October 2013 at 15:21:52 UTC, 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
shou
On Friday, 18 October 2013 at 16:01:30 UTC, Dicebot wrote:
On Friday, 18 October 2013 at 15:29:09 UTC, ilya-stromberg
wrote:
About syntax - we can use something like this:
log!(user, server, errorCode)(LOGIN_FAILED_UUID, "Couldn't log
in");
That will be template instance blo
Also, Tango have log module:
https://github.com/SiegeLord/Tango-D2/blob/d2port/tango/util/log/Log.d
For example, "Funkwerk IT Karlsfeld" use it because Phobos
haven't got logger:
http://dconf.org/talks/rohe.html
On Sunday, 20 October 2013 at 10:56:44 UTC, Robert Schadek 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
On Sunday, 20 October 2013 at 15:34:50 UTC, Sean Kelly wrote:
On Wednesday, 16 October 2013 at 07:18:39 UTC, ilya-stromberg
wrote:
Disagree. We need a log rotation support.
As I can see, available options could be:
* rotating conditions
- by date (rotate every hour, day (default), week, month
On Sunday, 20 October 2013 at 16:05:47 UTC, ilya-stromberg wrote:
On Sunday, 20 October 2013 at 15:34:50 UTC, Sean Kelly wrote:
On Wednesday, 16 October 2013 at 07:18:39 UTC, ilya-stromberg
wrote:
Disagree. We need a log rotation support.
As I can see, available options could be:
* rotating
On Monday, 21 October 2013 at 06:27:39 UTC, SomeDude wrote:
On Thursday, 17 October 2013 at 07:34:28 UTC, 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
On Monday, 21 October 2013 at 08:37:43 UTC, Robert Schadek wrote:
I for once have never seen any log API with
log.level = INFO;
Logger.log("Here be dragons");
And this I believe for a good reason: in 99% of production
code I've
seen, several log levels are mixed, i.e INFO, CRITICAL and
DEBUG f
On Sunday, 13 October 2013 at 13:12:35 UTC, Dicebot wrote:
On Sunday, 13 October 2013 at 12:12:08 UTC, ilya-stromberg
wrote:
Dicebot, Robert Klotzner would like to start review of the
`std.signal` module:
http://forum.dlang.org/post/siwjrbtfoyyafyvzd...@forum.dlang.org
If you are agree to be
On Friday, 8 November 2013 at 20:09:57 UTC, Martin Nowak wrote:
I made a wiki page for that.
Please discuss, improve and prioritize.
http://wiki.dlang.org/Agenda
Can we add this page to the wiki homepage, for example in "Core
Development" section? Probably, more people will see it.
On Sunday, 10 November 2013 at 11:32:45 UTC, Robert wrote:
On Sunday, 10 November 2013 at 10:37:41 UTC, Jacob Carlborg
wrote:
On 2013-11-09 23:50, Robert wrote:
1
Nice. But you trade it for protection having a default value,
making the
syntax more verbose in the general case.
You can overloa
On Sunday, 10 November 2013 at 15:30:29 UTC, Ilya Yaroshenko
wrote:
std.templatecons: Functional style template constructors.
If you want to add `std.templatecons` into Phobos I suggest you
to add your code to the Review Queue:
http://wiki.dlang.org/Review_Queue
If you think that your code i
On Thursday, 7 November 2013 at 13:45:57 UTC, Dicebot wrote:
Our current victim is std.signal by Robert Klotzner which is
supposed to deprecate and supersede existing (and broken)
std.signals
Robert, it will be great to see some more documentation for
`std.signal`.
For example, you can:
- a
Hi,
Do you know any library with support JSON-RPC for D?
Thanks.
On Sunday, 11 August 2013 at 16:06:42 UTC, Dicebot wrote:
On Sunday, 11 August 2013 at 08:51:19 UTC, ilya-stromberg wrote:
Hi,
Do you know any library with support JSON-RPC for D?
Thanks.
Don't know about direct JSON-RPC implementation, but using
vibe.http.rest from vibed.org allow
On Tuesday, 13 August 2013 at 15:04:38 UTC, Jacob Carlborg wrote:
There's a fully working example here:
https://dl.dropboxusercontent.com/u/18386187/docs/std.serialization/std_serialization_serializer.html
Sorry, I think that example is WRONG!
Your example:
void main ()
{
auto archive =
1 - 100 of 159 matches
Mail list logo
