FYI - mo' work on std.allocator

[Marco Leise via Digitalmars-d]

Am Tue, 06 May 2014 22:55:37 +0400
schrieb Dmitry Olshansky <dmitry.olsh at gmail.com>:

> 06-May-2014 10:20, Marco Leise пишет:
> > Am Mon, 05 May 2014 21:13:10 +0400
> > schrieb Dmitry Olshansky <dmitry.olsh at gmail.com>:
> >
> >> I had an idea of core.vmm. It didn't survive the last review though,
> >> plus I never got around to test OSes aside from Windows & Linux.
> >> Comments on initial design are welcome.
> >> https://github.com/D-Programming-Language/druntime/pull/653
> >
> > That's exactly what I had in mind and more. :)
> 
> Cool.
> I was ambitious at start until I released that there were about 5-6 
> logically consistent primitives of which many OS-es provided say 3 or 4 
> with little or inexact overlap. That's why I thought of focusing on 
> common recipes, and provide building blocks for them.

These subtle differences between OSs can kill every clean
design, hehe. The last time I thought about it I came to the
conclusion that some cross-platform APIs are better designed
more around use-cases than blindly mapping OS functions. I.g.
both chmod() and an opaque integer are bad abstractions for
file attributes.

> > These are all free functions that can be used as building
> > blocks for more specific objects. Was there a dedicated review
> > thread on the news group? All I could find was a discussion
> > about why not to use a VMM struct with static functions as
> > a namespace replacement.
> 
> I don't recall such but I think I did a tiny topic on it in general D NG.

You probably mean the same thread:
http://forum.dlang.org/thread/l4u68b$30fo$1@digitalmars.com

-- 
Marco