Re: Example Attached

On 10.02.2009 19:51, Heinz wrote: Heinz Wrote: I attached a rar file with the sources just to see what i'm talking about. The example is from the DMD site. Included is the extern D (ok) and the extern C (fails). To compile open "compile.bat" and to run the programs use "run.bat". Try this: a

Re: Constants?

For more documentation: d1: const: final: invariant: enums: d2

Re: Structuring a library project—best practi ces

On Thu, Feb 12, 2009 at 6:02 AM, Zarathustra wrote: > Hello Joel > > Maybe, you should look on the Helix Library. > www.dsource.org/projects/helix Well, I wouldn't recommend you copy their idea of having a single top-level template that encloses all your types[1]. AFAIK, that doesn't have any be

Re: Constants?

On Wed, Feb 11, 2009 at 4:09 PM, Mike L. wrote: > Could someone lay out for me the different ways of doing constants in D (d1, > particularly)? I've heard things about const, final, invariant, and > "anonymous enums"? > OK, D1 doesn't have constness in the way that C/C++ and D2 do. D1 only has

Re: Structuring a library project—best practices?

On Thu, Feb 12, 2009 at 4:39 AM, Joel C. Salomon wrote: > I'm starting work on my Geometric Algebra library > , and I'd like some tips on > structuring the source tree. Is there a "standard" place to put the > library test/demonstration? > > Right now I'm star

Constants?

Could someone lay out for me the different ways of doing constants in D (d1, particularly)? I've heard things about const, final, invariant, and "anonymous enums"?

Re: Structuring a library project—best practices

Hello Joel Maybe, you should look on the Helix Library. www.dsource.org/projects/helix But in my opinion you should write down all classes which You want to implement in your library, and then all relations between these classes. This approach warrants you essentially correct structure. I don't

Structuring a library project—best practices ?

I’m starting work on my Geometric Algebra library , and I’d like some tips on structuring the source tree. Is there a “standard” place to put the library test/demonstration? Right now I’m starting with: trunk/ gald/ e2.d test.d ds

Re: Internal error: ..\ztc\evalu8.c 2093

It is really strange, but when I removed dsss and tango with dmd, and then put them back. The problem disappeared. I still use DSSS 0.78 and Tango 0.99.7 with DMD 1.033.

Re: Internal error: ..\ztc\evalu8.c 2093

John Reimer wrote: Hello Zarathustra, When I trying build dwt-win 3.4.1 I get the following error: Internal error: ..\ztc\evalu8.c 2093 command line: dsss build I using DSSS 0.78, Tango 0.99.7 with DMD 1.033. OS: Windows XP Any ideas? Can you try a more recent compiler... like dmd 1.037?