On Saturday, 28 March 2015 at 19:52:15 UTC, IgorStepanov wrote:
http://wiki.dlang.org/DIP66
First I want to apologize for the long absence.
I was very busy for those months and now I ready to continue
the work.
This DIP has been approved with three clarifications:
about is-expression, about o
Congratz Andrei and Sanda
Java has disruptor to provide the fatest way to ring file.
website: http://lmax-exchange.github.io/disruptor/
technical information:
http://lmax-exchange.github.io/disruptor/files/Disruptor-1.0.pdf
What about hugepagesize system on LINUX ?
On Saturday, 28 March 2015 at 22:53:54 UTC, Timothee Cour wrote:
If there's no easy way to do it, there should be a way (eg a
compiler
option) to throw an exception on null pointer access. Even if
it's unsafe,
it would help for debugging (eg printing relevant application
specific
context). This
On Thu, Mar 26, 2015 at 9:13 PM, deadalnix via Digitalmars-d <
digitalmars-d@puremagic.com> wrote:
> On Friday, 27 March 2015 at 03:59:30 UTC, zhmt wrote:
>
>>
>>> The best way to do that is to separate the server modules into
>>> independent processes. Then if one crashes, the others keep running
http://wiki.dlang.org/DIP66
First I want to apologize for the long absence.
I was very busy for those months and now I ready to continue the
work.
This DIP has been approved with three clarifications:
about is-expression, about opDispatch and about "common"
inheritance.
I've reflected those c
https://github.com/D-Programming-Language/dlang.org/pull/946
On 2015-03-27 19:27:37 +, Martin Nowak said:
On Friday, 27 March 2015 at 19:00:16 UTC, Chris wrote:
"Also, and this counts for something I think, Go is a trendy
language right now, so when it comes to recruiting, I think
having Go as a critical part of Repustate’s tech stack will help."
St
I'd like to see D with GUI framework like JUCE. That's what would make
me use D more. For now I'll stick with C++ and JUCE. I know it sounds
superficial to have your choice of language based so much on GUI, but I
write software for average people to use, not for other programmers (and
not for s
D has documented unittests (they appear in the docs as if part
of the Examples section). The only excuses for example code in
Phobos to be untested are supposed to be that it is an
incomplete fragment or that it is old code from before we had
the feature.
— David
I added some just recentl
You can clear the input stream:
while(getchar() != '\n') {};
Or just use readln:
int resp = readln.chomp.to!int;
On Friday, 27 March 2015 at 18:38:32 UTC, rumbu wrote:
schwartzSort it's a nice name only if you are German.
Hardly. The name's just as meaningless on its own. It may be
easier for us Germans to remember the spelling, but even we have
to memorize that "tz", as "schwarz" (black) is more common
On Sunday, 22 March 2015 at 01:44:32 UTC, weaselcat wrote:
On Sunday, 22 March 2015 at 01:24:10 UTC, Martin Nowak wrote:
On Saturday, 21 March 2015 at 23:49:26 UTC, Atila Neves wrote:
I actually think that there are two large categories of
programmers: those like writing the same loops over and
On Saturday, 28 March 2015 at 00:01:48 UTC, Jesse Phillips wrote:
Probably should be Identifier for consistency [e.g. _arugments,
__vptr, _ctor]
Isn't __ctor just a DMD thing? I don't think we should be
highlighting symbols which aren't guaranteed to even exist for a
particular implementation
On Saturday, 28 March 2015 at 03:07:31 UTC, jonaspm wrote:
module main;
import std.stdio;
import std.string;
int main(string[] args)
{
int resp;
char[] p, q;
writefln("MENU DE OPCIONES");
writefln("1) Modus Ponens");
writefln("2) Modus Tollens");
writefln("3) Silo
On 2015-03-28 01:01, Jesse Phillips wrote:
Statement [e.g. debug, return, function, with] (that needs fixed)
Not sure what you mean.
Probably should be Identifier for consistency [e.g. _arugments, __vptr,
_ctor]
I completely forgot about these. Should these be the same as __ctfe?
Which I
On 3/26/15, Vladimir Panteleev via Digitalmars-d
wrote:
> What is your use case for only logging specific exception types?
We already have scope(failure) with its defined semantics (it will not
swallow the exception), changing that would be bad. So the only
workable solution I see is to extend it
18 matches
Mail list logo
