On Tuesday, 21 April 2015 at 14:10:36 UTC, Johannes Pfau wrote:
Am Tue, 21 Apr 2015 11:42:40 +
schrieb "Jens Bauer" :
I'm still hoping for a solution to this. Should I file a
bug-report ?
Didn't this[1] commit fix the problem?
I can confirm that the problem is fixed.
-And the code gener
On Tuesday, 21 April 2015 at 14:10:36 UTC, Johannes Pfau wrote:
Am Tue, 21 Apr 2015 11:42:40 + schrieb "Jens Bauer"
:
I'm still hoping for a solution to this. Should I file a
bug-report ?
Didn't this[1] commit fix the problem?
My mistake. I had my git repository stuck on a 2 week old
Am Tue, 21 Apr 2015 11:42:40 +
schrieb "Jens Bauer" :
> On Tuesday, 7 April 2015 at 19:31:25 UTC, Johannes Pfau wrote:
> > The recently added weak attribute shows a small difference in
> > behavior compared to c {snip}
> >
> > __attribute__((weak)) int test();
> >
> > (nil) 0
> >
On Tuesday, 7 April 2015 at 19:31:25 UTC, Johannes Pfau wrote:
The recently added weak attribute shows a small difference in
behavior compared to c {snip}
__attribute__((weak)) int test();
(nil) 0
@attribute("weak") void test();
=> unresolved symbol test
The problem
The recently added weak attribute shows a small difference in behavior
compared to c:
#include
__attribute__((weak)) int test();
int main()
{
printf("%p %d\n", &test, (int)&test);
return 0;
}
(nil) 0
import core.st
