d

Just curious if this is the best practice for initializing a dynamic, multidimensional array in D . There is a section on arrays in their language reference, but I'm not quite sure if it goes over what I'm trying to accomplish. class Map { Tile[][] tiles; this(uint width, uint height) { tiles.length = height; foreach (ref tilerow; tiles) tilerow.length = width; } } Map map1 = new Map(5000, 3000); // values determined at runtime (or an equivalent alternative like a typical for (y=0;y<height;y++) loop). My concern with this is that it reallocates each row of the array separately rather than the

I am trying to teach myself AI using neural networks. Long story short, I wanted to create a simple graphic that would display what is happening in my program using ncurses. The tutorial that I am using is found here . I was under the impression that D was compatible with C and I could theoretically call C functions relatively easily. I find that not to be the case. I am a relatively novice programmer, so even the simplistic explanations are a little above my head. I found this here . D is designed to fit comfortably with a C compiler for the target system. D makes up for not having its own VM

I'm trying to write a function in the D programming language to replace the calls to C's strtold. (Rationale: To use strtold from D, you have to convert D strings to C strings, which is inefficient. Also, strtold can't be executed at compile time.) I've come up with an implementation that mostly works, but I seem to lose some precision in the least significant bits. The code to the interesting part of the algorithm is below and I can see where the precision loss comes from, but I don't know how to get rid of it. (I've left out a lot of the parts of code that weren't relevant to the core

I'm learning D from 8 years in C++. My question is with regards to D garbage collection - when do I use delete, and when don't I need to? You don't. Delete is not to be used with D version 2 and intended to be removed from the language. What the hold up is, I am not sure. Instead you use a function, destroy (object), which calls the destructor where you can free resources that are not GC memory. The destructor will be caused again during GC collection of the objects own memory. This is explained in " The D Programming Language ". The idea is to reclaim resources earlier than what the GC would

I download the GDC for Linux , and try to build a simple D Program. After executing " gdc hello.d -o hello ", it outputs: [root@localhost nan]# gdc hello.d -o hello /usr/bin/ld: unrecognized option '-plugin' /usr/bin/ld: use the --help option for usage information collect2: error: ld returned 1 exit status Then I use " gdc -v hello.d -o hello " command, and try to find the root cause. It displays: ...... COLLECT_GCC_OPTIONS='-v' '-o' 'hello' '-shared-libgcc' '-mtune=generic' '-march=x86-64' /home/nan/x86_64-gdcproject-linux-gnu/bin/../libexec/gcc/x86_64-unknown-linux-gnu/4.9.0/collect2 -plugin

Does D have an exit statement, similar to the one in java, python, c/c++. Which will (big shocker) exit execution of the program? Something like exit(); If you want exit , then use C's exit function. import core.stdc.stdlib; void main() { exit(-1); } I'm not quite sure how that affects the D runtime and whatnot though. It might be that stuff doesn't get cleaned up like you'd normally want, or it might be just fine. I wouldn't really advise using it in general though, since there are usually better ways to handle exiting a program. But the declaration for the C function is in druntime, so it's