It's not a module ctor, this code is executed much earlier. You
can write a function, which will initialize standard streams, and
call it from the C code before rt_init.
On Friday, 5 September 2014 at 07:22:23 UTC, hane wrote:
On Thursday, 4 September 2014 at 15:10:22 UTC, Jorge A. S.
wrote:
I'm having an error related to yours: when I call writeln
function in a closed stdout I will get a segfault message.
Example:
import std.stdio;
void main() {
stdout.clo
On Thursday, 4 September 2014 at 20:57:41 UTC, Kagamin wrote:
https://github.com/D-Programming-Language/druntime/blob/master/src/rt/dmain2.d#L270
well, this sucks.
Is there a way I can call module c-tors explicitly?
I was under impression that D(dmd) was suppose to work with
VisualC++ in x64b
On Thursday, 4 September 2014 at 15:10:22 UTC, Jorge A. S. wrote:
I'm having an error related to yours: when I call writeln
function in a closed stdout I will get a segfault message.
Example:
import std.stdio;
void main() {
stdout.close();
write("hello\n");
}
The code above will crash wi
https://github.com/D-Programming-Language/druntime/blob/master/src/rt/dmain2.d#L270
well, this sucks.
https://github.com/D-Programming-Language/druntime/blob/master/src/core/stdc/stdio.d#L457
see? It's null. Hmm... where is it initialized?
On Thursday, 4 September 2014 at 20:38:38 UTC, Kagamin wrote:
Maybe some module constructor wasn't run due to linking mess.
So it remains uninitialized.
Is there a way I can check if module c-tor run? rt_init()
returned no error.
Maybe some module constructor wasn't run due to linking mess. So
it remains uninitialized.
On Thursday, 4 September 2014 at 18:22:55 UTC, Marc Schütz wrote:
On Thursday, 4 September 2014 at 17:57:47 UTC, Szymon Gatner
wrote:
On Thursday, 4 September 2014 at 15:25:59 UTC, ketmar via
Digitalmars-d-learn wrote:
On Thu, 04 Sep 2014 15:10:21 +
"Jorge A. S. via Digitalmars-d-learn"
wr
On Thursday, 4 September 2014 at 17:57:47 UTC, Szymon Gatner
wrote:
On Thursday, 4 September 2014 at 15:25:59 UTC, ketmar via
Digitalmars-d-learn wrote:
On Thu, 04 Sep 2014 15:10:21 +
"Jorge A. S. via Digitalmars-d-learn"
wrote:
In one of the specializations of the write function in the
s
On Thursday, 4 September 2014 at 15:25:59 UTC, ketmar via
Digitalmars-d-learn wrote:
On Thu, 04 Sep 2014 15:10:21 +
"Jorge A. S. via Digitalmars-d-learn"
wrote:
In one of the specializations of the write function in the
std.stdio (the call site that you showed in your post) no
check for c
On Thu, 04 Sep 2014 15:10:21 +
"Jorge A. S. via Digitalmars-d-learn"
wrote:
> In one of the specializations of the write function in the
> std.stdio (the call site that you showed in your post) no check
> for closed stdout (when stdout._p is null) is done. I can't say
> if this is a bug in
I'm having an error related to yours: when I call writeln
function in a closed stdout I will get a segfault message.
Example:
import std.stdio;
void main() {
stdout.close();
write("hello\n");
}
The code above will crash with segfault buf the following code
will raise an exception instead
On Wednesday, 3 September 2014 at 09:55:55 UTC, Szymon Gatner
wrote:
Hey,
I am trying to build hybrid (C++, D) application (more here:
http://forum.dlang.org/thread/ugkpqprobonorbdun...@forum.dlang.org)
but I am now getting assertion failure from within writeln().
writeln() is called from a D
Hey,
I am trying to build hybrid (C++, D) application (more here:
http://forum.dlang.org/thread/ugkpqprobonorbdun...@forum.dlang.org)
but I am now getting assertion failure from within writeln().
writeln() is called from a D function that has C++ linkage:
D definition:
extern (C++) void pri
15 matches
Mail list logo
