version assignment and module scope
dcrepid via Digitalmars-d-learn
digitalmars-d-learn at puremagic.com
Mon Sep 15 15:38:50 PDT 2014
> 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 the explanation. I hadn't considered that
putting a version assignment between imports, but I see how that
can become an issue.
More information about the Digitalmars-d-learn
mailing list