no. it works the way it's intended to work. given that order of
module
imports is not defined (i.e. reordering imports should not
affect
resulting code), making 'version=' propagating to other modules
will
create disasterous side effects, even weirder than C macro
abusing.
Okay, thanks for th
On Mon, 15 Sep 2014 21:26:27 +
dcrepid via Digitalmars-d-learn
wrote:
> Could this be considered a defect of design?
no. it works the way it's intended to work. given that order of module
imports is not defined (i.e. reordering imports should not affect
resulting code), making 'version=' prop
I'm a bit baffled why using something like this doesn't get
recognized by imported modules:
version = Unicode;
I use this to try and alter the way the win32 API headers resolve
certain symbols, but currently the only way to force that version
symbol to be recognized correctly is to define it
