On Monday, 1 September 2014 at 00:19:43 UTC, Adam D. Ruppe wrote:
On Monday, 1 September 2014 at 00:10:25 UTC, Abe wrote:
Is this roughly the same on all relevant platforms for DMD?
Yeah. If you used printf instead of writeln, the size gets down
to about 250K (on my linux anyway), which can
On 01/09/14 02:10, Abe wrote:
Thanks, Adam.
Is this roughly the same on all relevant platforms for DMD?
I was thinking [hoping?] that maybe this was a problem vis-a-vis the Mac
OS X linker, i.e. a situation such that the linker isn`t dropping
anything from the referenced libraries, even when
Thanks, Adam.
Is this roughly the same on all relevant platforms for DMD?
I was thinking [hoping?] that maybe this was a problem vis-a-vis
the Mac OS X linker, i.e. a situation such that the linker isn`t
dropping anything from the referenced libraries, even when the
majority of the stuff in
On Monday, 1 September 2014 at 00:10:25 UTC, Abe wrote:
Is this roughly the same on all relevant platforms for DMD?
Yeah. If you used printf instead of writeln, the size gets down
to about 250K (on my linux anyway), which can then be stripped
down to 160K, showing that the rest of the size
Compared to them, D programs are small. The big difference is
Java, .net, ruby, python, etc. are already popular enough to
have their libraries/support code pre-installed on the user's
computer. D programs, on the other hand, carry all their
support code with them in each executable (they're
On Monday, 1 September 2014 at 00:56:35 UTC, Abe wrote:
It would be nice to have an option to use a systemwide library
file and dynamically link it; that way, as a silly example,
You can do it on Linux with dmd right now (use dmd
-defaultlib=libphobos2.so when building), but I don't know
