Hi Peter,
I would argue that it is "os.arch" which is a bit of a mess, because it
attempts to represent too much in a single name. Compare this with the set
of "triples" here :
http://llvm.org/doxygen/classllvm_1_1Triple.html
I would argue that these definitions would be a more useful way to
Hi Peter,
I would argue that it is "os.arch" which is a bit of a mess, because it
attempts to represent too much in a single name. Compare this with the set
of "triples" here :
http://llvm.org/doxygen/classllvm_1_1Triple.html
I would argue that these definitions would be a more useful way to
In my experience it is quite often handy to have a separate API bundle -
yours is one use case, another is where the system may run on different
platforms which require different implementations for some services (cloud
vs development machine, embedded vs dev, self-contained demo vs real
