V Thu, 14 Jan 2016 17:32:47 +
NX via Digitalmars-d-learn napsáno:
> Please explain.
Regression: something works before does not work anymore
Bug: something does not work as expected (regression is one type of bug)
Please explain.
I was expecting that DUB / DMD & NMAKE take $LIB into account. I try to
compile some stuff on x64.
This is LIB:
D:\develop\d-language\webchat> $Env:lib
C:\Program Files (x86)\Microsoft Visual Studio
14.0\VC\LIB\amd64;C:\Program Files (x86)\Microsoft Visual Studio
On Thursday, 14 January 2016 at 02:35:28 UTC, Josh Phillips wrote:
On Wednesday, 13 January 2016 at 20:08:55 UTC, Dav1d wrote:
Link with opengl32.lib
How? Everywhere I looked it says this cannot be done due to
conflicting formats between the dmd compiler and the windows
one.
Welcome to D
On Thursday, 14 January 2016 at 09:25:50 UTC, Dav1d wrote:
On Thursday, 14 January 2016 at 02:35:28 UTC, Josh Phillips
wrote:
On Wednesday, 13 January 2016 at 20:08:55 UTC, Dav1d wrote:
Link with opengl32.lib
How? Everywhere I looked it says this cannot be done due to
conflicting formats
On Wednesday, 13 January 2016 at 18:35:29 UTC, Ilya Yaroshenko
wrote:
Ok, great. BTW: What is Mir?
https://github.com/DlangScience/mir --Ilya
Nice.
On 01/13/2016 11:41 PM, Jacob Carlborg wrote:
> what if I need to format a third party type that I cannot add
> methods to? UFCS does not seem to work.
Here is an experiment that wraps the third party type to provide a lazy
toString:
import std.stdio;
import std.format;
import std.array;
On Thursday, 14 January 2016 at 22:13:37 UTC, Robert M. Münch
wrote:
Seems that some paths in sc.ini were not setup correctly. For
x64 a Win10-SDK directory which doesn't exists was referenced.
Did you install DMD manually? In that case, you will usually need
to edit sc.ini to point to
On 2016-01-14 17:59, Ali Çehreli wrote:
Here is an experiment that wraps the third party type to provide a lazy
toString:
import std.stdio;
import std.format;
import std.array;
import std.algorithm;
import std.range;
/* Wraps an element and provides a lazy toString that dispatches the
work to
Returning a struct with a destructor and not binding it to a
variable appears to make the destructor run immediately instead
of at the end of the scope.
Is this intended?
example:
http://dpaste.dzfl.pl/dd285200ba2b
On 01/14/2016 09:23 PM, rsw0x wrote:
> Returning a struct with a destructor and not binding it to a variable
> appears to make the destructor run immediately instead of at the end of
> the scope.
> Is this intended?
>
> example:
> http://dpaste.dzfl.pl/dd285200ba2b
Assuming that this rule is the
On Thursday, 14 January 2016 at 09:42:50 UTC, Dav1d wrote:
On Thursday, 14 January 2016 at 09:25:50 UTC, Dav1d wrote:
On Thursday, 14 January 2016 at 02:35:28 UTC, Josh Phillips
wrote:
Welcome to D and Windows. You can use GDC or LDC or try
On Thursday, January 14, 2016 08:41:23 Jacob Carlborg via Digitalmars-d-learn
wrote:
> On 2016-01-13 22:20, H. S. Teoh via Digitalmars-d-learn wrote:
>
> > Isn't that just a matter of replacing each of the segments with their
> > range equivalents? Also, std.format.formattedWrite will do
> >
On 2016-01-14 17:40:44 +, Robert M. Münch said:
I was expecting that DUB / DMD & NMAKE take $LIB into account. I try to
compile some stuff on x64.
This is LIB:
D:\develop\d-language\webchat> $Env:lib
C:\Program Files (x86)\Microsoft Visual Studio
14.0\VC\LIB\amd64;C:\Program Files
14 matches
Mail list logo