Again, all we need to do is use a different macro than the default one.
In hindsight, using D_Ddoc is a mistake as the user does not want to
generate docs for Phobos but she does want to import stuff from it.
Andrei
On 2/6/11 8:44 PM, Jason House wrote:
On Feb 6, 2011, at 6:58 PM, Jonathan M Davis <[email protected]
<mailto:[email protected]>> wrote:
You really shouldn't be compiling with ddoc enabled unless you're
building the
documentation. There are just too many cases where you need separate
declarations for ddoc - often because of differences between OSes.
There are
cases where the ddoc version is different _on purpose_. In the case of
std.file.DirEntry.isDir, it's const on Windows because it can be. But
because it
can't be on Linux, the ddoc version doesn't list it that way. Now,
maybe it's on
negligble benefit to have isDir const on Windows given that it can't
be on Linux,
but there are definitely cases where ddoc is forced to be different
from a
particular OS' version of a declaration, simply because that
declaration is
different on different systems.
Do _not_ expect your code to work if you compile with ddoc enabled.
Such requirements feel like a failure of design. Are there any lessons
learned from these kinds of problems? I'm sure Walter did not intend
separate ddoc versions.
_______________________________________________
dmd-beta mailing list
[email protected]
http://lists.puremagic.com/mailman/listinfo/dmd-beta
_______________________________________________
dmd-beta mailing list
[email protected]
http://lists.puremagic.com/mailman/listinfo/dmd-beta
