Proposal: this.d

[Kirk McDonald]

Jari-Matti Mäkelä wrote:
> Bill Baxter wrote:
>>In Python, probably the most common usage of the __init__.py module is
>>as a place to stuff package-specific documentation.  It's also supposed
>>to list, but not import, the modules that should be imported by an
>>"import package.*".  This solves the problem of .* pulling in unrelated
>>cruft.
> 

(The Python syntax is actually "from package import *", but I'm just 
being pedantic by pointing that out.)

> 
> Agreed. I didn't say .* was perfect, it just solves some problems. I could
> say test files and other private implementation should be perhaps in some
> nested package, but that would make the package modifier partly useless.
> Package level documentation would be a very nice thing, but on the other
> hand if the compiler would allow e.g. declarations inside this.d, some
> tools would need special support for D. Maybe this is a limitation in the
> tools?

Why wouldn't declarations be allowed in this.d? It's just another module 
with a curious way of importing it.

-- 
Kirk McDonald
http://kirkmcdonald.blogspot.com
Pyd: Connecting D and Python
http://pyd.dsource.org