April 05, 2012
On Thursday, April 05, 2012 23:47:52 David wrote:
> Am 05.04.2012 23:10, schrieb ReneSac:
> > Ok, that page gives some pointers. Seems like I shouldn't use std.stream. So, std.cstream or std.stdio are safe?
> 
> I also heared that, but actually std.stream works pretty well, especially the EndianStream. So I can recommend you to use it.

Regardless of how well it works, it's going to be replaced with a range-based API. So, it's not going to be around in the long run. You can use it. You just have to be aware that it's going to go away. Unfortunately, its replacement is far from ready, so we really don't know when it's actually going to be replaced.

- Jonathan M Davis
April 06, 2012
On 4/6/2012 7:42 AM, ReneSac wrote:

>> Most people use DMD, but GDC, I hear, should be on par.
>
> I don't need a 64bit binary right now. Actually, I would even prefer a
> 32bit one for development because then I can't run too wild in memory
> usage. The problem is that DMD seems to require 32 bit windows,
> according to the page I linked... Is it not true?

DMD runs just fine on 64-bit Windows.
April 07, 2012
On Friday, 6 April 2012 at 01:33:10 UTC, Mike Parker wrote:
> DMD runs just fine on 64-bit Windows.
Then why "32 bit Windows (Win32) operating system, such as Windows XP" is put as a requirement? This should be corrected: http://dlang.org/dmd-windows.html

Anyway, in the mean time I have setup GDC using the latest binaries, and it is working well.

The only thing I noticed is that a simple "Hello World" took several seconds to compile, and ended up with 1.25MB (release, non-debug build)! And I thought that D was fast to compile... But then I discovered that switching to std.c.stdio made the compilation almost instantaneous, and the executable size a slightly more reasonable 408KB. It works, but that isn't really an option, as D strings aren't readily compatible with C strings...

I know that the lower limiter in binary size is higher, due to the statically compiled runtime, but this "bloat" in the std lib for a single function worries me a bit. Is DMD better in this measurement, or is it a limitation of the current D libraries?

This may be kinda important latter, as in compression benchmarks, the decompressor size is added in the compressed size to prevent cheating. I don't want a multi-megabyte executable size.

April 07, 2012
On 07.04.2012 8:51, ReneSac wrote:
> On Friday, 6 April 2012 at 01:33:10 UTC, Mike Parker wrote:
>> DMD runs just fine on 64-bit Windows.
> Then why "32 bit Windows (Win32) operating system, such as Windows XP"
> is put as a requirement? This should be corrected:
> http://dlang.org/dmd-windows.html
>
> Anyway, in the mean time I have setup GDC using the latest binaries, and
> it is working well.
>
> The only thing I noticed is that a simple "Hello World" took several
> seconds to compile, and ended up with 1.25MB (release, non-debug build)!

how about strip it?
+ MinGW debug info is notoriously bloated (if it was debug build).

> And I thought that D was fast to compile... But then I discovered that
> switching to std.c.stdio made the compilation almost instantaneous, and
> the executable size a slightly more reasonable 408KB. It works, but that
> isn't really an option, as D strings aren't readily compatible with C
> strings...
>
> I know that the lower limiter in binary size is higher, due to the
> statically compiled runtime, but this "bloat" in the std lib for a
> single function worries me a bit. Is DMD better in this measurement, or
> is it a limitation of the current D libraries?
>
> This may be kinda important latter, as in compression benchmarks, the
> decompressor size is added in the compressed size to prevent cheating. I
> don't want a multi-megabyte executable size.
>


-- 
Dmitry Olshansky
April 07, 2012
On Saturday, 7 April 2012 at 06:21:16 UTC, Dmitry Olshansky wrote:
> On 07.04.2012 8:51, ReneSac wrote:
>> The only thing I noticed is that a simple "Hello World" took several
>> seconds to compile, and ended up with 1.25MB (release, non-debug build)!
>
> how about strip it?
> + MinGW debug info is notoriously bloated (if it was debug build).

I said it was a non-debug build. The debug build for the "Hello World" is 7.6MB.


1 2
Next ›   Last »