Thread overview
import("dir/file") does not work
May 18, 2016
Vadim Lopatin
May 18, 2016
Atila Neves
May 18, 2016
Vadim Lopatin
May 18, 2016
Andrew Chamberlain
May 18, 2016
Andrew Chamberlain
May 18, 2016
Vadim Lopatin
May 18, 2016
Hello,

Is it intended that import of file as array does not work if path is specified for import file name?

import("dir/file.ext"); // does not work
import("file.ext"); // works if dir is added to -J list

I believe it would be convenient if I could just specify one -J path (e.g. -Jviews) and import any file from nested directories just by providing relative path from one of -J dirs.

(checked on latest DMD under Windows; replacing / with \\ does not help)


Best regards,
     Vadim

May 18, 2016
On Wednesday, 18 May 2016 at 05:11:51 UTC, Vadim Lopatin wrote:
> Hello,
>
> Is it intended that import of file as array does not work if path is specified for import file name?
>
> import("dir/file.ext"); // does not work
> import("file.ext"); // works if dir is added to -J list
>
> I believe it would be convenient if I could just specify one -J path (e.g. -Jviews) and import any file from nested directories just by providing relative path from one of -J dirs.
>
> (checked on latest DMD under Windows; replacing / with \\ does not help)
>
>
> Best regards,
>      Vadim

That was a bug that was recently fixed.

Atila
May 18, 2016
On Wednesday, 18 May 2016 at 06:47:08 UTC, Atila Neves wrote:
> On Wednesday, 18 May 2016 at 05:11:51 UTC, Vadim Lopatin wrote:
>> Hello,
>>
>> Is it intended that import of file as array does not work if path is specified for import file name?
>>
>> import("dir/file.ext"); // does not work
>> import("file.ext"); // works if dir is added to -J list
>>
>> I believe it would be convenient if I could just specify one -J path (e.g. -Jviews) and import any file from nested directories just by providing relative path from one of -J dirs.
>>
>> (checked on latest DMD under Windows; replacing / with \\ does not help)
>>
>>
>> Best regards,
>>      Vadim
>
> That was a bug that was recently fixed.
>
> Atila

Thank you!
It looks like it's not yet included into recent DMD beta available for download.



May 18, 2016
On Wednesday, 18 May 2016 at 11:58:46 UTC, Vadim Lopatin wrote:
> On Wednesday, 18 May 2016 at 06:47:08 UTC, Atila Neves wrote:
>> On Wednesday, 18 May 2016 at 05:11:51 UTC, Vadim Lopatin wrote:
>>>      [...]
>>
>> That was a bug that was recently fixed.
>>
>> Atila
>
> Thank you!
> It looks like it's not yet included into recent DMD beta available for download.

in nightly perhaps ?

https://dlang.org/download.html#dmd-nightly
May 18, 2016
On Wednesday, 18 May 2016 at 12:16:47 UTC, Andrew Chamberlain wrote:
> On Wednesday, 18 May 2016 at 11:58:46 UTC, Vadim Lopatin wrote:
>> On Wednesday, 18 May 2016 at 06:47:08 UTC, Atila Neves wrote:
>>> On Wednesday, 18 May 2016 at 05:11:51 UTC, Vadim Lopatin wrote:
>>>>      [...]
>>>
>>> That was a bug that was recently fixed.
>>>
>>> Atila
>>
>> Thank you!
>> It looks like it's not yet included into recent DMD beta available for download.
>
> in nightly perhaps ?
>
> https://dlang.org/download.html#dmd-nightly

the latest beta is always for a "point" release so it only includes regressions fixed from the previous "discrete" (.0) release, not the bug fixed since the "discrete" release to the "point" release.
May 18, 2016
On Wednesday, 18 May 2016 at 12:20:14 UTC, Andrew Chamberlain wrote:
>>> Thank you!
>>> It looks like it's not yet included into recent DMD beta available for download.
>>
>> in nightly perhaps ?
>>
>> https://dlang.org/download.html#dmd-nightly
>
> the latest beta is always for a "point" release so it only includes regressions fixed from the previous "discrete" (.0) release, not the bug fixed since the "discrete" release to the "point" release.

Thank you! Working on nightly build.