On Saturday, 3 December 2016 at 16:07:47 UTC, moe wrote:
On Sunday, 11 September 2016 at 02:17:21 UTC, Vlasov Roman
wrote:
Hello, guys.
I tried to build HelloWorld with dub, but i got strange linker
error:
[...]
I just switched from Windows to linux (arch) and got the exact
same problem.
On 2016-12-05 07:44, unDEFER wrote:
Hello! I have compiled libdb (BerkeleyDB) with Microsoft Visual Studio
2015.
1) "Debug" mode. I have libdb53d.dll file. Do implib.
The linker doesn't seen symbols from the library! Do "lib -l". In the
list of symbols "db_create", linker searches "_db_create". I
Hello! I have compiled libdb (BerkeleyDB) with Microsoft Visual
Studio 2015.
1) "Debug" mode. I have libdb53d.dll file. Do implib.
The linker doesn't seen symbols from the library! Do "lib -l". In
the list of symbols "db_create", linker searches "_db_create". Is
it the problem?
2) "Debug-Static
On Sunday, December 04, 2016 15:30:22 vladdeSV via Digitalmars-d-learn
wrote:
> Hello!
>
> I have a question not directly related to D as it is with coding
> standards.
>
> My issue at hand is if I have one variable for a class, which I
> want to be directly accessible for anything else, should it
I've been using Appender quite a bit recently, typically when I
need append-only arrays with variable and unknown final sizes. I
had been prepared to write a custom data structure when I started
using it with large amounts of data, but very nicely this has not
surfaced as a need. Appender has h
On Sunday, 4 December 2016 at 15:30:22 UTC, vladdeSV wrote:
Are there any other reasons to use get/setters?
basically, no. as you can omit parentheses in D, converting to
getter/setter later should be seamless.
the only reason to have getter/setter in your case is a situation
where you may
On Sunday, 4 December 2016 at 15:30:22 UTC, vladdeSV wrote:
Hello!
I have a question not directly related to D as it is with
coding standards.
My issue at hand is if I have one variable for a class, which I
want to be directly accessible for anything else, should it be
1. public, or
2. pr
Hello!
I have a question not directly related to D as it is with coding
standards.
My issue at hand is if I have one variable for a class, which I
want to be directly accessible for anything else, should it be
1. public, or
2. private, with @property get/setters?
From what I have been tol
On Tuesday, 29 November 2016 at 00:05:31 UTC, Steven
Schveighoffer wrote:
hashOf is kind of this horrible hacky thing that nobody should
be using. It literally takes whatever you pass it and hashes
the local bytes.
Ugg... Anything with pointers, classes or arrays will have huge
problems with
On Sunday, 4 December 2016 at 06:51:24 UTC, Tofu Ninja wrote:
So what is the proper way to get the hash of something now?
This question came up a few days ago:
http://forum.dlang.org/post/o1igoc$21ma$1...@digitalmars.com
On Sunday, 4 December 2016 at 08:32:23 UTC, Mike Parker wrote:
On Sunday, 4 December 2016 at 08:30:40 UTC, Mike Parker wrote:
your shader, print out the result of glGetString(GL_VERSION) to
Alternatively, since you're using Derelict, you can check the
return value of DerelictGL3.reload() or,
On Sunday, 4 December 2016 at 08:30:40 UTC, Mike Parker wrote:
your shader, print out the result of glGetString(GL_VERSION) to
Alternatively, since you're using Derelict, you can check the
return value of DerelictGL3.reload() or, any time after calling
it, DerelictGL3.loadedVersion.
On Sunday, 4 December 2016 at 06:41:07 UTC, Payotz wrote:
So I've been trying to teach myself how to OpenGL, and there
are errors whenever I try to compile my shaders.
Errors are : http://i.imgur.com/5hRaQL8.png
Why the screenshot? Simpler to respond to copy/pasted text.
The second line is a
13 matches
Mail list logo
