• Jeremy DeHaan (4/4) Dec 12 2014 Is this on purpose? Granted, I almost never use interface files,
• Jonathan M Davis via Digitalmars-d-learn (6/10) Dec 13 2014 It probably was never considered. But given that all that's really suppo...

"Jeremy DeHaan" <dehaan.jeremiah gmail.com> writes:

Is this on purpose? Granted, I almost never use interface files, 
but I had a whim to use them for what I was working on today.

Everything worked fine when I renamed the file to package.d, but 
apparently package.di is not acceptible.

Jonathan M Davis via Digitalmars-d-learn writes:

On Saturday, December 13, 2014 02:34:21 Jeremy DeHaan via Digitalmars-d-learn
wrote:
 Is this on purpose? Granted, I almost never use interface files,
 but I had a whim to use them for what I was working on today.

 Everything worked fine when I renamed the file to package.d, but
 apparently package.di is not acceptible.

It probably was never considered. But given that all that's really supposed
to be put in a package.d file is public imports, it's not like supporting
package.di really adds much, though arguably it should work for
consistency's sake.

- Jonathan M Davis