http://d.puremagic.com/issues/show_bug.cgi?id=11172
--- Comment #6 from Andrej Mitrovic <[email protected]> 2013-10-04 13:02:45 PDT --- (In reply to comment #5) > My recommendation is that library developers need to eschew using generic > version > identifiers, and instead use a prefix consisting of the library name. Yeah. I'm doing this in my own libraries too. But since each library practically owns the toplevel package name (each library name is unique, after all), we could avoid depending on naming conventions and instead allow using the package or module name before an identifier: version (foolib.SharedLib) { } Then from the command line you would call: $ dmd -lib -version=foolib.SharedLib foolib.d Is it overkill? The alternative is to manually encode the name and use `version=foolib_SharedLib`, but it's a bit ugly. I could see some use-cases: version=std.perf_tests => enable performance test suite in all of phobos version=std.datetime.perf_tests => enable the same just for datetime Of course these would still be visible globally, but there's no need for name encoding conventions if this is allowed. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------
