On Mon, 01 May 2006 23:15:17 -0600, Hasan Aljudy wrote:

> Derek Parnell wrote:
>> On Mon, 01 May 2006 19:08:28 +1000, Hasan Aljudy <hasan.aljudy@gmail.com>  wrote:
>> 
>>> It's not build's fault, and there really isn't any effecient way to always figure out the filename if it doesn't match the module name.
>> 
>> Yes I know that, so what I'm considering is allowing a .mfm (module-file-mapping) file to be placed on the command line to help Build  resolve import names. This might replace the all.d hack too.
>> 
> 
> but that defeats the point of using build.

I know ;-) but if people are going to use module references that don't follow the (implied) standards then they might appreciate the help. Plus I'm thinking that the .mfm file could be a way of implementing the "import package.*" idea that Java people like so much.

I'll think on it a bit more ...

-- 
Derek
(skype: derek.j.parnell)
Melbourne, Australia
"Down with mediocracy!"
2/05/2006 3:17:45 PM