On 07/25/2016 07:11 PM, ketmar via Digitalmars-d-learn wrote:
On Tuesday, 26 July 2016 at 01:19:49 UTC, Charles Hixson wrote:
then I will prefer the core.stdc.stdio approach. I find it's
appearance extremely much cleaner...
only if you are really used to write C code. when you see pointer, or
explicit type size argument in D, it is a sign of C disease.
I'll probably wrap those routines in a struct to ensure things like
files being properly closed, and not have explicit pointers
persisting over large areas of code.
exactly what std.stdio.File did! ;-)
Yes, but I really despise the syntax they came up with. It's probably
good if most of your I/O is ranges, but mine hasn't yet ever been.
(Combining ranges with random I/O?)
