Re: Reason for mypackage/package.d instead of mypackage.d

2014-11-10 Thread Steven Schveighoffer via Digitalmars-d-learn
On 11/10/14 4:33 PM, Dicebot wrote: On Monday, 10 November 2014 at 21:25:32 UTC, Jonathan Marler wrote: I was perusing a PR for phobos where std/range.d was split into submodules and std/range.d was moved to std/range/package.d I was wondering why a package module had to be called "package.d" i

Re: Reason for mypackage/package.d instead of mypackage.d

2014-11-10 Thread Dicebot via Digitalmars-d-learn
On Monday, 10 November 2014 at 21:25:32 UTC, Jonathan Marler wrote: I was perusing a PR for phobos where std/range.d was split into submodules and std/range.d was moved to std/range/package.d I was wondering why a package module had to be called "package.d" instead of just being the package na

Reason for mypackage/package.d instead of mypackage.d

2014-11-10 Thread Jonathan Marler via Digitalmars-d-learn
I was perusing a PR for phobos where std/range.d was split into submodules and std/range.d was moved to std/range/package.d I was wondering why a package module had to be called "package.d" instead of just being the package name. For example, instead of moving std/range.d to std/range/package