On Thu, 15 Jul 2010 00:22:34 +0200, Jonathan M Davis
jmdavisp...@gmail.com wrote:
I was wondering what the general consesus was (if there is one) on
whether it's
valuable to always put module declarations in each module.
Obviously, if you need the module to have a name other than the file
On 15.07.2010 21:59, Rory McGuire wrote:
From what I remember in TDPL:
Can be used to rename a module if you have it in a different directory
structure than how you use it. E.g. implementation and headers in
separate folders.
If you use *.di files (headers), you would normally just keep the
On Thu, 15 Jul 2010 23:08:07 +0200, torhu n...@spam.invalid wrote:
On 15.07.2010 21:59, Rory McGuire wrote:
From what I remember in TDPL:
Can be used to rename a module if you have it in a different directory
structure than how you use it. E.g. implementation and headers in
separate folders.
I was wondering what the general consesus was (if there is one) on whether it's
valuable to always put module declarations in each module.
Obviously, if you need the module to have a name other than the file name, then
you need to have the module declaration. However, is it necessarily
On 15.07.2010 00:22, Jonathan M Davis wrote:
I was wondering what the general consesus was (if there is one) on whether it's
valuable to always put module declarations in each module.
Obviously, if you need the module to have a name other than the file name, then
you need to have the module
