a wrote:
QML looks like it is (currently ?) targeted at the kind of GUI programming
when you make your own custom widgets for everything. It only provides the
most basic components such as rectangles, text, and images. There isn't,
say, a button components - you have to make one using a
I also did a little benchmarks. Here is the results:
Time for multiplying two 1000x1000 matrics:
clang 2.8 (-O3)2.4s
gcc 4.4.5 (-O3)2.5s
ldc2 llvm-2.9 (-O3 -release) 2.7s
gdc2 4.4.6 (-O3 -frelease -finline)2.9s
dmd
1500x1500:
Currently, as far as I know, there are only two lexers and two parsers for
D: the C++ front end which dmd, gdc, and ldc use and the D front end which
ddmd uses and which is based on the C++ front end. Both of those are under
the GPL (which makes them useless for a lot of stuff) and both of
I've noticed that the issue tracker tab on the LDC2 project
(https://bitbucket.org/prokhin_alexey/ldc2/overview) is missing. First,
why is it missing?
I disabled it on purpose, because I am going to delete my branch soon and work
directly with ldc main repository.
Second, if it's missing
LDC2 Status
LDC2 passes almost all phobos unittests and tests from dmd suite on linux x86.
Also it probably works on freebsd, but it's broken on other platforms and
architectures.
I currently work on linux X86_64 port: ldc2 already compiles druntime and
phobos, although there are some serious
Still can't get druntime to compile. The readme file in runtime/ is
horribly outdated. I cloned your github repo, and tried a few things,
but I have no clue where I should put it, or how to build it. It looks
like the make file is still for DMD.
I use cmake to compile druntime and phobos:
$
