What strategies do library authors have for maintaining two versions of a their
code - one for D 1.0 and another for 2.0? When they make changes to one
version, do they manually copy them into the other branch? Or is there a way of
automating the process?
Version blocks don't seem to help much.
On Wed, 10 Jun 2009 04:30:53 -0400, John C wrote:
> What strategies do library authors have for maintaining two
> versions of a their code - one for D 1.0 and another for 2.0?
> When they make changes to one version, do they manually copy
> them into the other branch? Or is there a way of automati
Daniel Keep Wrote:
>
>
> Jason House wrote:
> > Earlier today, I tried to use the D compiler for .NET from
> > http://dnet.codeplex.com/
> >
> > Beyond compilation of the compiler, I found zero instructions on what to do
> > next. How do I integrate the compiler into the .NET framework/visua
Jason House Wrote:
> Beyond compilation of the compiler, I found zero instructions on what to do
> next.
I believe it's a traditional CUI compiler. Compile the compiler, open command
prompt and run the compiler with source files. I think, it will say if
something is wrong.
> How do I integrate
Kagamin Wrote:
> Jason House Wrote:
> > I'd like to be able to add D files to existing solutions (with C#
> > code).
> I don't think this feature is available, the author was focused on making CUI
> compiler only. If VS allows integration of 3rd party compilers, you can use
> that.
> BTW how d
im building a large dictionary program, which could possibly grow up to 100gb
in size for word collection alone. im not very familiar with GC and memory
paging. is there any library to enable me control ram usage with paging? Thanks.
Jason House Wrote:
>What I'm really hoping to get out of this is proper generic programming and
>enhanced compile-time validation.
>
I think these are done by frontend and frontend was kept intact. He didn't even
wanted to add .net-specific pragmas to the frontend.
LDC is a moving target because it's actively developed, and generally things
improve with time.
This is a recent change by the quite active Frits van Bommel:
http://www.dsource.org/projects/ldc/changeset/1486%3A9ed0695cb93c
This is a cleaned up version discussed in this thread:
import tango.stdc
Daniel Keep Wrote:
> "The back-end code is not of production quality, it is intended for
> research and educational purposes. The D Programming Language is a
> fairly complex language, and non-trivial features such as TLS and
> closures make it an interesting case study for generating IL code."
On Wed, Jun 10, 2009 at 2:12 PM, Jason House wrote:
> Daniel Keep Wrote:
>
>> "The back-end code is not of production quality, it is intended for
>> research and educational purposes. The D Programming Language is a
>> fairly complex language, and non-trivial features such as TLS and
>> closures ma
On Tue, 09 Jun 2009 19:35:51 +0200, Saaa wrote:
>>> What kind of fall-throughs were these?
>>>
>>> A:
>>>
>>> case value1:
>>> case value2:
>>> case valueN:
>>> code1();
>>> break;
>>>
>>> B:
>>>
>>> case value1:
>>> code1();
>>> case value2:
>>> code2();
>>> break;
>>
>> The s
Joel Christensen wrote:
See previous post.
12 matches
Mail list logo
