On Monday, 14 March 2016 at 09:57:19 UTC, stunaep wrote:

> It looks like _fseeki64 is in the nightly build but not dmd 2.070.2; However, the nightly build says std.stdio and std.conv are deprecated and I cant use them.

I think you may be misinterpreting the error message. There was a change recently in how imports are handled in certain cases and that may be what you're seeing. What exactly is the error message?

On Monday, 14 March 2016 at 13:33:36 UTC, Mike Parker wrote:
> On Monday, 14 March 2016 at 09:57:19 UTC, stunaep wrote:
>
>> It looks like _fseeki64 is in the nightly build but not dmd 2.070.2; However, the nightly build says std.stdio and std.conv are deprecated and I cant use them.
>
> I think you may be misinterpreting the error message. There was a change recently in how imports are handled in certain cases and that may be what you're seeing. What exactly is the error message?

I'm on my phone but I think It said something like
Deprecation: module std.stdio not accessible from here. Try import static std.stdio

On Monday, 14 March 2016 at 14:19:27 UTC, stunaep wrote:
> I'm on my phone but I think It said something like
> Deprecation: module std.stdio not accessible from here. Try import static std.stdio

That's fix for bug https://issues.dlang.org/show_bug.cgi?id=313
See the code where std.stdio is not accessible from.

On Monday, 14 March 2016 at 14:19:27 UTC, stunaep wrote:

>
> I'm on my phone but I think It said something like
> Deprecation: module std.stdio not accessible from here. Try import static std.stdio

Deprecation: module std.stdio is not accessible here, perhaps add 'static import std.stdio;'

The solution is right there in the error message. Change your import from whatever it is now to a static one. See [1].

[1] http://forum.dlang.org/thread/1835132.hmAZsairJU@lyonel