On Friday, 6 March 2015 at 02:41:19 UTC, Bennet wrote:
I wrote a custom OBJ file importer which worked fairly well
however was not robust enough to support everything. I've
decided to give AssImp a shot. I followed some tutorials and
have set up my code to read in the vertices, tex coords,
On Saturday, 7 March 2015 at 13:11:22 UTC, Rene Zwanenburg wrote:
On Friday, 6 March 2015 at 02:41:19 UTC, Bennet wrote:
I wrote a custom OBJ file importer which worked fairly well
however was not robust enough to support everything. I've
decided to give AssImp a shot. I followed some
On Saturday, 7 March 2015 at 23:48:39 UTC, Timothee Cour wrote:
I'm a little confused about the following:
clear,delete,destroy.
My understanding is that clear is deprecated and delete is
planned to be
deprecated, so we should only ever use destroy (which
deterministic calls
the destructor
On Saturday, 7 March 2015 at 21:19:47 UTC, Bennet wrote:
On Saturday, 7 March 2015 at 13:11:22 UTC, Rene Zwanenburg
wrote:
On Friday, 6 March 2015 at 02:41:19 UTC, Bennet wrote:
I wrote a custom OBJ file importer which worked fairly well
however was not robust enough to support everything.
I'm a little confused about the following:
clear,delete,destroy.
My understanding is that clear is deprecated and delete is planned to be
deprecated, so we should only ever use destroy (which deterministic calls
the destructor but doesn't release memory).
Unique uses delete however in the
On Thursday, March 05, 2015 21:54:01 weaselcat via Digitalmars-d-learn wrote:
Seems barely maintained and there was a proposed replacement
claiming it was broken(http://wiki.dlang.org/Review/std.signal)
that never got approved.
Is std.signals worth using over a dub package?
I think that the
On Friday, 6 March 2015 at 16:04:33 UTC, Benjamin Thaut wrote:
On Friday, 6 March 2015 at 15:36:47 UTC, anon wrote:
Hi,
I can't figure this out.
struct Pair(T)
{
T x;
T y;
alias x c;
alias y r;
}
What would like is that the x and y to be initialized to
different values depending on
On Saturday, 7 March 2015 at 09:39:42 UTC, Kagamin wrote:
On Saturday, 7 March 2015 at 02:23:10 UTC, zhmt wrote:
Hi,I got the right answer in vibe.d forum,here is the link:
http://forum.rejectedsoftware.com/groups/rejectedsoftware.vibed/thread/24403/#post-24416
If that's correct, you can
On 8/03/2015 2:49 p.m., Jason den Dulk wrote:
Hi
I noticed that in 32bit, many Phobos functions use int and uint, while
in 64bit, they use long and ulong. As a result I am having some
difficulty in writing code that works for both 32 bit and 64 bit. Is
there an existing mechanism that allows
To clarify, I'm only asking about a struct allocated via new.
Unique!T is wrapped around a struct, but it allocates a struct T via 'new',
so my question still holds: does 'delete t' (where t is a struct allocated
via new) guarantee deterministic destruction?
I'm guessing yes, otherwise Unique
Hi
I noticed that in 32bit, many Phobos functions use int and uint,
while in 64bit, they use long and ulong. As a result I am having
some difficulty in writing code that works for both 32 bit and 64
bit. Is there an existing mechanism that allows writing code that
will work in both 32 bit
11 matches
Mail list logo
