Re: Compiler error with static vars/functions

Thanks for the answer. This means that all classes belonging to the same module must be in the same *.d file? I mean not one *.d file per class as in most languages? Regards, Oliver Original-Nachricht > Datum: Thu, 09 Feb 2012 14:18:07 -0500 > Von: "Jonathan M D

Compiler error with static vars/functions

a bit strange for me. Apparently, must be some kind of import problem importing Foo. But I don't see how ... Thanks for any hints. Cheers, Oliver -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

Re: D with gmp via swig

== Quote from David Nadlinger (s...@klickverbot.at)'s article > On 8/14/11 3:03 PM, Oliver wrote: > > I did have to copy the libgmpd_wrap* to some place were the linker could > > find it, > > of course. > Alternatively, you could set LD_LIBRARY_PATH to where your l

Re: D with gmp via swig

== Quote from David Nadlinger (s...@klickverbot.at)'s article > On 8/14/11 2:34 PM, Oliver wrote: > > /opt/usr/local/bin/gdc main.d gmpd.d gmpd_im.d -I. -L. -lgmpd_wrap > You don't need to link the .so in (although I'm surprised to see that it > produces linker errors

Re: D with gmp via swig

definition in /tmp/ccmF49fr.o section .tbss mismatches non-TLS reference in ./libgmpd_wrap.so ./libgmpd_wrap.so: could not read symbols: Bad value collect2: ld returned 1 exit status again, a mismatch. Oliver

Re: D with gmp via swig

Thanks Iain, I'll contact the swig team about it. Oliver

D with gmp via swig

y_functions: TLS definition in gmpd_im.o section .tbss mismatches non-TLS reference in gmpd_wrap.o gmpd_wrap.o: could not read symbols: Bad value collect2: ld returned 1 exit status I have tried dmd and/or gcc (for the wrapper compilation and linking) but no joy. Also -fPIC did not help. Thanks, Oliver

Re: Pointer to Struct Pointer

== Quote from Stewart Gordon (smjg_1...@yahoo.com)'s article > On 19/02/2011 13:18, Oliver wrote: > > > > Hello, > > > > I have the following code that works. > What? The code you've posted doesn't work. Sorry for that, in the post I got the //

Re: Pointer to Struct Pointer

== Quote from bearophile (bearophileh...@lycos.com)'s article > Oliver: > > ... > struct Ts { > int d; > union { > int[] intData; > double[] doubleData; > } > } > struct Rs { > int i; > union { > int intDat

Pointer to Struct Pointer

Hello, I have the following code that works. I'd like to change the t tsData to ts tsData, but this does segfault. I do not understand how I dereferece the ts struct correctly. Perhaps someone could give me a hint. Thanks. Oliver - alias rs *r; alias ts *t; struct ts {

Re: Semantics of range::put

I found out that an "appender" or operator ~= will work, but still do not understand why put makes the program terminate. Oliver Kanai Wrote: > Hello, > according to my understanding of the "put" method for ranges, which is part > of the output-range interfa

Re: Semantics of range::put

I found out that an "appender" or operator ~= will work, but still do not understand why put makes the program terminate. Oliver Kanai Wrote: > Hello, > according to my understanding of the "put" method for ranges, which is part > of the output-range interfa

Semantics of range::put

ut("Hallo"); it compiles but does not execute: the compiler gives the message core.exception.asserter...@std.array(256): Assertion failure Best regards, Oliver