On Thursday, 25 October 2012 at 17:20:40 UTC, Rob T wrote:
On Thursday, 25 October 2012 at 02:15:41 UTC, Jakob Ovrum wrote:
You can even share the same GC between dynamic libraries and
the host application (if both are D and use GC, of course)
using the GC proxy system.
What is the GC proxy
On Thursday, 25 October 2012 at 17:17:01 UTC, Rob T wrote:
Yes I can build my own D shared libs, both as static PIC (.a)
and dynamically loadable (.so). however I cannot statically
link my shared libs to druntime + phobos as-is. The only way I
can do that, is to also compile druntime + phobos i
On Thursday, 25 October 2012 at 17:17:01 UTC, Rob T wrote:
Yes I can build my own D shared libs, both as static PIC (.a)
and dynamically loadable (.so). however I cannot statically
link my shared libs to druntime + phobos as-is. The only way I
can do that, is to also compile druntime + phobos i
On Thursday, 25 October 2012 at 02:15:41 UTC, Jakob Ovrum wrote:
You can even share the same GC between dynamic libraries and
the host application (if both are D and use GC, of course)
using the GC proxy system.
What is the GC proxy system, and how do I make use of it?
--rt
On Thursday, 25 October 2012 at 08:50:19 UTC, Jakob Ovrum wrote:
You are right that compiling the runtime itself (druntime and
Phobos) as a shared library is not yet fully realized, but that
doesn't stop you from compiling your own libraries and
applications as shared libraries even if they sta
On Thursday, 25 October 2012 at 08:34:15 UTC, Rob T wrote:
My understanding of dynamic linking and the runtime is based on
this thread
http://www.digitalmars.com/d/archives/digitalmars/D/dynamic_library_building_and_loading_176983.html
The runtime is not compiled to be sharable, so you cannot
On Thursday, 25 October 2012 at 02:15:41 UTC, Jakob Ovrum wrote:
You can very much link to C and C++ code, or have C and C++
code link to your D code, while still using the GC, you just
have to be careful when you send GC memory to external code.
You can even share the same GC between dynami
