On Friday, 3 April 2015 at 04:55:42 UTC, Mike Parker wrote:
On Thursday, 2 April 2015 at 09:38:05 UTC, Namespace wrote:
Dgame is based on SDL 2.0.3 (as described in the installation
tutorial), but tries to wrap any function call which is
introduced after SDL 2.0.0:
static if
On Friday, 3 April 2015 at 17:10:33 UTC, Dicebot wrote:
On Friday, 3 April 2015 at 17:03:35 UTC, Atila Neves wrote:
. Separate compilation. One file changes, only one file gets
rebuilt
This immediately has caught my eye as huge no in the
description. We must ban C style separate compilation,
On Friday, 3 April 2015 at 17:13:41 UTC, Dicebot wrote:
Also I don't see any point in yet another meta build system.
The very point of initial discussion was about getting D only
cross-platform solution that won't require installing any
additional software but working D compiler.
I was also
I wanted to work on this a little more before announcing it, but
it seems I'm going to be busy working on trying to get
unit-threaded into std.experimental so here it is:
http://code.dlang.org/packages/reggae
If you're wondering about the name, it's because it's supposed to
build on dub.
On Friday, 3 April 2015 at 17:03:35 UTC, Atila Neves wrote:
. Separate compilation. One file changes, only one file gets
rebuilt
This immediately has caught my eye as huge no in the
description. We must ban C style separate compilation, there is
simply no way to move forward otherwise. At
Also I don't see any point in yet another meta build system. The
very point of initial discussion was about getting D only
cross-platform solution that won't require installing any
additional software but working D compiler.
On Friday, 3 April 2015 at 17:17:50 UTC, Atila Neves wrote:
On Friday, 3 April 2015 at 17:13:41 UTC, Dicebot wrote:
Also I don't see any point in yet another meta build system.
The very point of initial discussion was about getting D only
cross-platform solution that won't require installing
On Friday, 3 April 2015 at 17:59:22 UTC, Atila Neves wrote:
Well, I took your advice (and one of my acceptance tests is
based off of your simplified real-work example) and started
with the low-level any-command-will-do API first. I built the
high-level ones on top of that. It doesn't seem
On 2015-03-18 12:14:01 +, Vladimir Panteleev said:
I've pushed support for DMD bootstrapping, so if you need to build
master now, build latest Digger from source. I'll make a binary release
after 2.067 is out.
Any news on this?
And will there by COFF32 support as well?
--
Robert M.
On Friday, 3 April 2015 at 17:25:51 UTC, Ben Boeckel wrote:
On Fri, Apr 03, 2015 at 17:10:31 +, Dicebot via
Digitalmars-d-announce wrote:
On Friday, 3 April 2015 at 17:03:35 UTC, Atila Neves wrote:
. Separate compilation. One file changes, only one file gets
rebuilt
This immediately
On Friday, 3 April 2015 at 17:40:42 UTC, Dicebot wrote:
On Friday, 3 April 2015 at 17:17:50 UTC, Atila Neves wrote:
On Friday, 3 April 2015 at 17:13:41 UTC, Dicebot wrote:
Also I don't see any point in yet another meta build system.
The very point of initial discussion was about getting D only
On Friday, 3 April 2015 at 17:22:42 UTC, Atila Neves wrote:
On Friday, 3 April 2015 at 17:10:33 UTC, Dicebot wrote:
On Friday, 3 April 2015 at 17:03:35 UTC, Atila Neves wrote:
. Separate compilation. One file changes, only one file gets
rebuilt
This immediately has caught my eye as huge no
On Friday, 3 April 2015 at 17:55:00 UTC, Dicebot wrote:
On Friday, 3 April 2015 at 17:25:51 UTC, Ben Boeckel wrote:
On Fri, Apr 03, 2015 at 17:10:31 +, Dicebot via
Digitalmars-d-announce wrote:
On Friday, 3 April 2015 at 17:03:35 UTC, Atila Neves wrote:
. Separate compilation. One file
On 2015-04-03 20:06, Atila Neves wrote:
Interesting.
It's true that it's not always faster to compile each module separately,
I already knew that. It seems to me, however, that when that's actually
the case, the practical difference is negligible. Even if 10x slower,
the linker will take
On Friday, 3 April 2015 at 19:07:09 UTC, Jacob Carlborg wrote:
On 2015-04-03 20:06, Atila Neves wrote:
Interesting.
It's true that it's not always faster to compile each module
separately,
I already knew that. It seems to me, however, that when that's
actually
the case, the practical
On 2015-04-03 19:03, Atila Neves wrote:
I wanted to work on this a little more before announcing it, but it
seems I'm going to be busy working on trying to get unit-threaded into
std.experimental so here it is:
http://code.dlang.org/packages/reggae
One thing I noticed immediately (unless I'm
If you are interested, we are doing a GUI system inspired by
QtQuick/QMLEngine :
https://github.com/D-Quick/DQuick
On Friday, 3 April 2015 at 19:08:58 UTC, weaselcat wrote:
I just tried compiling one of my project. It has a makefile
that does separate compilation and a shell script I use for
unit testing which compiles everything in one go. The makefile
takes 5.3 seconds, does not including linking since
On 4/3/15 12:07 PM, Jacob Carlborg wrote:
On 2015-04-03 20:06, Atila Neves wrote:
Interesting.
It's true that it's not always faster to compile each module separately,
I already knew that. It seems to me, however, that when that's actually
the case, the practical difference is negligible.
On Friday, 3 April 2015 at 18:06:42 UTC, Atila Neves wrote:
All I know is I've seen a definite improvement in my
edit-compile-unittest cycle by compiling modules separately.
How would the decoupling happen? Is the user supposed to
partition the binary into suitable static libraries? Or is the
On Friday, 3 April 2015 at 16:43:38 UTC, Robert M. Münch wrote:
On 2015-03-18 12:14:01 +, Vladimir Panteleev said:
I've pushed support for DMD bootstrapping, so if you need to
build master now, build latest Digger from source. I'll make a
binary release after 2.067 is out.
Any news on
On Friday, 3 April 2015 at 17:55:00 UTC, Dicebot wrote:
On Friday, 3 April 2015 at 17:25:51 UTC, Ben Boeckel wrote:
On Fri, Apr 03, 2015 at 17:10:31 +, Dicebot via
Digitalmars-d-announce wrote:
On Friday, 3 April 2015 at 17:03:35 UTC, Atila Neves wrote:
. Separate compilation. One file
On 4/3/15 11:06 AM, Atila Neves wrote:
It's true that it's not always faster to compile each module separately,
I already knew that. It seems to me, however, that when that's actually
the case, the practical difference is negligible. Even if 10x slower,
the linker will take longer anyway.
On 4/3/15 10:10 AM, Dicebot wrote:
On Friday, 3 April 2015 at 17:03:35 UTC, Atila Neves wrote:
. Separate compilation. One file changes, only one file gets rebuilt
This immediately has caught my eye as huge no in the description. We
must ban C style separate compilation, there is simply no
One small note about the tutorials. In the tutorial on
Game Loop and Event handling:
http://rswhite.de/dgame5/?page=tutorialtut=handle_events
In the first example, I believe you are missing an import for
Dgame.Window.Event. It shows up int the second example, so no big
deal, but I figured I
Hi folks,
today i've created my first dlang library ^_^ a binding to the
OpenVG library standard. The referenced implementation is ShivaVG
which allows to draw vector graphics within an OpenGL context
(similar to cairo).
A small demo application is included, using derelict gl3 and glfw3
On 4/04/2015 11:53 a.m., ddos wrote:
Hi folks,
today i've created my first dlang library ^_^ a binding to the OpenVG
library standard. The referenced implementation is ShivaVG which allows
to draw vector graphics within an OpenGL context (similar to cairo).
A small demo application is included,
27 matches
Mail list logo
