https://issues.dlang.org/show_bug.cgi?id=17747
Walter Bright changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://issues.dlang.org/show_bug.cgi?id=17747
Martin Nowak changed:
What|Removed |Added
Keywords||pull
CC|
https://issues.dlang.org/show_bug.cgi?id=17747
anonymous4 changed:
What|Removed |Added
See Also||https://issues.dlang.org/sh
|
https://issues.dlang.org/show_bug.cgi?id=17747
--- Comment #15 from anonymous4 ---
(In reply to Steven Schveighoffer from comment #14)
> Changing the link order does nothing, because there is one file.
It requires two files to work.
> In other words, issue 7063 is a bug, no matter how you build
https://issues.dlang.org/show_bug.cgi?id=17747
--- Comment #14 from Steven Schveighoffer ---
Changing the link order does nothing, because there is one file.
In other words, issue 7063 is a bug, no matter how you build it. It shouldn't
build (hence accepts-invalid).
This proposal is different -
https://issues.dlang.org/show_bug.cgi?id=17747
--- Comment #13 from anonymous4 ---
Looks like it.
--
https://issues.dlang.org/show_bug.cgi?id=17747
--- Comment #12 from Steven Schveighoffer ---
(In reply to anonymous4 from comment #11)
> (In reply to Steven Schveighoffer from comment #10)
> > There is also no other precedent where a compiled D program only works
> > properly if you link in the c
https://issues.dlang.org/show_bug.cgi?id=17747
--- Comment #11 from anonymous4 ---
(In reply to Steven Schveighoffer from comment #10)
> There is also no other precedent where a compiled D program only works
> properly if you link in the correct order.
Issue 7063
--
https://issues.dlang.org/show_bug.cgi?id=17747
--- Comment #10 from Steven Schveighoffer ---
(In reply to anonymous4 from comment #9)
> (In reply to Steven Schveighoffer from comment #8)
> > People are used to this "just working".
> Same problem for other usage of extern(C).
How so?
void foo();
https://issues.dlang.org/show_bug.cgi?id=17747
--- Comment #9 from anonymous4 ---
(In reply to Steven Schveighoffer from comment #8)
> People are used to this "just working".
Same problem for other usage of extern(C).
--
https://issues.dlang.org/show_bug.cgi?id=17747
--- Comment #8 from Steven Schveighoffer ---
(In reply to anonymous4 from comment #7)
> C abi is requested with extern(C) here, sure they are different.
Essentially, what I'm saying is:
mod1.d:
int x;
extern(C) static this()
{
x = 5;
}
mod2.d:
https://issues.dlang.org/show_bug.cgi?id=17747
--- Comment #7 from anonymous4 ---
(In reply to Steven Schveighoffer from comment #6)
> D static ctors
C abi is requested with extern(C) here, sure they are different.
--
https://issues.dlang.org/show_bug.cgi?id=17747
Steven Schveighoffer changed:
What|Removed |Added
CC||schvei...@yahoo.com
Severit
https://issues.dlang.org/show_bug.cgi?id=17747
--- Comment #5 from ZombineDev ---
> It can be called in start before main, without DRuntime.
Agreed.
--
https://issues.dlang.org/show_bug.cgi?id=17747
--- Comment #4 from ZombineDev ---
> __attribute__ ((constructor)) is in C. It can be called in start before main,
> without DRuntime.
Technically this is a compiler extension, not a feature part of the ISO C
standard. My point was that C standard
https://issues.dlang.org/show_bug.cgi?id=17747
--- Comment #3 from Илья Ярошенко ---
(In reply to ZombineDev from comment #2)
> AFAIK, C doesn't have static constructors, only C++ has, so your example
> should be:
>
> extern(C++) shared static this()
> {
> // ...
> }
>
> Of course extern (D
https://issues.dlang.org/show_bug.cgi?id=17747
ZombineDev changed:
What|Removed |Added
Keywords||betterC, C++
CC|
https://issues.dlang.org/show_bug.cgi?id=17747
--- Comment #1 from Илья Ярошенко ---
And extern(C++), extern(D) can/should work too.
--
18 matches
Mail list logo