On Wednesday, 2 November 2016 at 11:17:49 UTC, Jonathan M Davis
wrote:
version(DIGITAL_MARS_STDIO)
extern(C) int setmode(int, int) nothrow @nogc;
else version(MICROSOFT_STDIO)
{
extern(C) int _setmode(int, int) nothrow @nogc;
alias setmode = _setmode;
}
It really should be put in
On Thursday, 3 November 2016 at 08:04:45 UTC, Jonathan M Davis
wrote:
[...]
Thank you for a detailed clarification about setmode
availability. I'll think more about how to proceed with it, and
whether I should request it in druntime.
I will try to make a bug report about deprecation.
On Thursday, November 03, 2016 03:25:31 Kirill Kryukov via Digitalmars-d-
learn wrote:
> Thanks for the explanation, Jonathan! OK, I'll try adding my own
> binding for the time being, and submit a feature request.
>
> I guess this does not count as regression since it was
> undocumented, as you
On Wednesday, 2 November 2016 at 11:17:49 UTC, Jonathan M Davis
wrote:
setmode was never publicly documented, and technically, you
weren't supposed to be using it from there (since it wasn't
documented). It was fixed in 2.072.0 so that all of the
undocumented stuff in std.stdio was made
e), the
> second one fails with these messages:
>
> a.d(6): Deprecation: std.stdio.setmode is not visible from module
> a
> a.d(6): Error: function std.stdio.setmode is not accessible from
> module a
>
> 2.072.0 changelog does not seem to mention anything relevant. Is
> ther
C:\utl\dev\D\dmd-2.072.0\windows\bin\dmd.exe a.d -ofa2.exe
The first one succeeds (producing a working executable), the
second one fails with these messages:
a.d(6): Deprecation: std.stdio.setmode is not visible from module
a
a.d(6): Error: function std.stdio.setmode is not accessible from
