digitalmars.D.learn - Is it legal to use std.windows modules?
- FreeSlave (4/4) Apr 08 2016 std.windows.syserror and others have documentation comments, but
- Jonathan M Davis via Digitalmars-d-learn (20/24) Apr 08 2016 I don't know why they're missing from the bar on the left on the website...
- zabruk70 (3/4) Apr 09 2016 old bug
- Adam D. Ruppe (5/9) Apr 11 2016 For what it is worth, my dpldocs.info site is able to document it:
- Vladimir Panteleev (7/11) Apr 11 2016 They were documented a while ago:
- Vladimir Panteleev (5/8) Apr 11 2016 Err, to correct/expand on that, the documentation has propagated,
std.windows.syserror and others have documentation comments, but they are not listed in online documentation on dlang.org. Is it ok to use functions and classes from this modules in D applications?
Apr 08 2016
On Friday, April 08, 2016 22:50:05 FreeSlave via Digitalmars-d-learn wrote:std.windows.syserror and others have documentation comments, but they are not listed in online documentation on dlang.org. Is it ok to use functions and classes from this modules in D applications?I don't know why they're missing from the bar on the left on the website. The documentation is there, even if it's not actually linked to properly. And std.windows.charset _is_ listed on the index page even if it's not on the bar on the left. std.windows.registry is actually used by std.datetime, so that's not going anywhere, and std.windows.syserror gets used by various of the I/O relate modules, so I very much doubt that it's going anywhere either. The only one that's guaranteed to be going away is std.windows.iunknown, because it's being replaced by core.sys.windows.com and is currently deprecated. std.windows.charset should arguably go away given that we advise that folks always use the W functions and don't actually, officially support anything older than Windows 7, and the W functions have been around since at least Win2K. But I doubt that it's going anywhere, and _someone_ out there is probably using it in their code even if they really shouldn't. So, if anything, I'd open a bug report about how std.windows is missing from the docs rather than assume that std.windows isn't supposed to be used. Presumably, it just got lost in some of the refactoring that's happened to the website in the last year or two. - Jonathan M Davis
Apr 08 2016
On Saturday, 9 April 2016 at 02:14:48 UTC, Jonathan M Davis wrote:So, if anything, I'd open a bug report about how std.windows isold bug https://issues.dlang.org/show_bug.cgi?id=13516
Apr 09 2016
On Friday, 8 April 2016 at 22:50:05 UTC, FreeSlave wrote:std.windows.syserror and others have documentation comments, but they are not listed in online documentation on dlang.org. Is it ok to use functions and classes from this modules in D applications?For what it is worth, my dpldocs.info site is able to document it: http://dpldocs.info/experimental-docs/std.windows.html and there's nothing in the source about it being private, so you should be ok using it.
Apr 11 2016
On Friday, 8 April 2016 at 22:50:05 UTC, FreeSlave wrote:std.windows.syserror and others have documentation comments, but they are not listed in online documentation on dlang.org. Is it ok to use functions and classes from this modules in D applications?They were documented a while ago: http://dlang.org/phobos-prerelease/std_windows_syserror.html https://issues.dlang.org/show_bug.cgi?id=14972 Due to a simple omission, the documentation has not propagated from /phobos-prerelease/ to /phobos/: https://github.com/D-Programming-Language/dlang.org/pull/1265
Apr 11 2016
On Tuesday, 12 April 2016 at 02:23:40 UTC, Vladimir Panteleev wrote:http://dlang.org/phobos-prerelease/std_windows_syserror.htmlDue to a simple omission, the documentation has not propagated from /phobos-prerelease/ to /phobos/:Err, to correct/expand on that, the documentation has propagated, it's simply not in the navigation: http://dlang.org/phobos/std_windows_syserror.html
Apr 11 2016