On 09/04/10 23:11, bearophile wrote:
BCS:
For example, having foo_linux.d and foo_win.d both claiming to be foo.
OK.
And I presume you don't want to use a single module with a mega version(linux)
{...} else {...} inside.
Thank you,
bearophile
No need for a huge module, or module names mismatching file names:
----
module foo;
version (linux) import foo_linux;
version (Windows) import foo_linux;
----
Sure it adds and extra file, it's a lot cleaner imo than having a huge
module with both implementations or mismatching file/module names.
