On 06/28/2016 08:39 PM, MMJones wrote:
> Yeah, I saw that. I'm looking the general answer though. Not just for
> GC. Does D basically combine the d files in to phobos when they are
> modified?
No. Somebody must explicitly build the library.
However, any code that's templated cannot be pre-built
On Wednesday, 29 June 2016 at 03:10:10 UTC, thedeemon wrote:
On Wednesday, 29 June 2016 at 02:18:27 UTC, MMJones wrote:
I read somewhere that one can modify the D files from phobos
and runtime to supply a stub for the GC. I would like to add
some logging features to the GC.
You don't need to
On Wednesday, 29 June 2016 at 02:18:27 UTC, MMJones wrote:
I read somewhere that one can modify the D files from phobos
and runtime to supply a stub for the GC. I would like to add
some logging features to the GC.
You don't need to recompile anything, a stub can be installed
from your progra
On 2016-06-29 14:39, Hiemlick Hiemlicker wrote:
Yes, the C standard requires malloc to be aligned to the platform size(4
for 32bit, 8 for 64-bit).
just what i was hopping for. thanks!
On Wednesday, 29 June 2016 at 02:24:55 UTC, captaindet wrote:
is there an alignment guarantee for core.stdc.stdlib.malloc?
more specifically, using DMD and compiling for 32bit on
windows, can i assume proper alignment for int or uint
variables?
background: i like to re-use a (ubyte) buffer,
is there an alignment guarantee for core.stdc.stdlib.malloc?
more specifically, using DMD and compiling for 32bit on windows, can i
assume proper alignment for int or uint variables?
background: i like to re-use a (ubyte) buffer, sometimes it will store
only bytes, sometimes it shall store ui
I read somewhere that one can modify the D files from phobos and
runtime to supply a stub for the GC. I would like to add some
logging features to the GC.
Does this not require one to recompile phobos? I figured the
source code was just for debugging?
I'm curious if I can really get away wit
On Monday, 27 June 2016 at 21:17:52 UTC, Thalamus wrote:
Hi everyone,
I've succeeded in using D as a client for regular (registered)
COM servers in the past, but in this case, I'm building the
server as well. I would like to avoid registering it if
possible so XCOPY-like deployment remains an
