On Monday, 6 June 2016 at 16:51:20 UTC, Jonathan Marler wrote:
Hmmm...it seems to be missing quite alot though. Especially
the winsock api. Over the weekend I was writing some code that
uses a windows IOCompletionPort and had to add a fair amount of
code that was missing:
Pull requests
On Monday, 6 June 2016 at 17:11:44 UTC, Vladimir Panteleev wrote:
On Monday, 6 June 2016 at 16:51:20 UTC, Jonathan Marler wrote:
Hmmm...it seems to be missing quite alot though.
You could've mentioned you meant just the winsock modules.
They have not been brought over because they were not
On Monday, 6 June 2016 at 16:51:20 UTC, Jonathan Marler wrote:
Hmmm...it seems to be missing quite alot though.
You could've mentioned you meant just the winsock modules.
They have not been brought over because they were not explicitly
under an open-source license.
On Monday, 6 June 2016 at 16:13:48 UTC, Vladimir Panteleev wrote:
On Monday, 6 June 2016 at 16:04:30 UTC, Jonathan Marler wrote:
I'm writing some platform specific D code and I've found that
what the druntime exposes for the windows platform is pretty
lean. I'm guessing that the purpose of
With the newest dmds, if you use -m32mscoff you just use the
Microsoft libraries and linkers and the core.sys.windows is
pretty full - should be easy to use.
On Monday, 6 June 2016 at 16:04:30 UTC, Jonathan Marler wrote:
I'm writing some platform specific D code and I've found that
what the druntime exposes for the windows platform is pretty
lean. I'm guessing that the purpose of the druntime version of
the windows api is to implement the minimum
I'm writing some platform specific D code and I've found that
what the druntime exposes for the windows platform is pretty
lean. I'm guessing that the purpose of the druntime version of
the windows api is to implement the minimum required to support
the windows platform and not meant to be a
