http://d.puremagic.com/issues/show_bug.cgi?id=5005
--- Comment #2 from Austin Hastings <ah0801...@yahoo.com> 2010-10-06 14:23:59 PDT --- BOP, That approach would look like: libs/ ... + myLib/ ... | .... + all.d And it would (probably?) work. But I am trying to *hide* the details - I don't want user code to change if I elect to split a module into implemenation parts. So I'd like to start by coding libs/ ... + myLib.d And then later, when it grows too big, change to: libs/ ... | myLib.d ... | myLib/ ... | .... | part1.d ... | .... | part2.d And have the user code none the wiser. If you'd like to see a real-world example of why this is a good idea, have a look at the std.*.d files. A bunch of them are already straining at the seams with unrelated classes, templates, etc. And adding more unittests just makes the situation worse. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------
