On Monday, 8 February 2016 at 07:05:15 UTC, Suliman wrote:
Cool! Thanks! But do you have any plans to reimplement it from
Pascal to В to get it's more native...
B?
What is B?
V Sun, 07 Feb 2016 23:47:39 +
Matt Elkins via Digitalmars-d-learn
napsáno:
> On Sunday, 7 February 2016 at 23:11:34 UTC, anonymous wrote:
> > On 07.02.2016 23:49, Matt Elkins wrote:
> >> Oi. Yes, I can, but it is quite a lot of code even if you
> >>
On Monday, 8 February 2016 at 07:25:49 UTC, Dominikus Dittes
Scherkl wrote:
On Monday, 8 February 2016 at 07:05:15 UTC, Suliman wrote:
Cool! Thanks! But do you have any plans to reimplement it from
Pascal to В to get it's more native...
B?
What is B?
Sorry, D
On Sunday, 7 February 2016 at 00:48:54 UTC, Jason White wrote:
I'm interested in feedback on this library. What is it missing?
How can be better?
I like what I've seen so far, but I'd just like to note that it's
easier to give feedback on the API when there is web
documentation. GitHub Pages
On Sunday, 7 February 2016 at 02:46:39 UTC, Marco Leise wrote:
My code would not see much ref counting in performance critical
loops. There is no point in ref counting every single point in
a complex 3D scene.
I could imagine it used on bigger items. Textures for example
since they may be used
https://issues.dlang.org/show_bug.cgi?id=15651
Issue ID: 15651
Summary: filter: only parameters or stack based variables can
be inout
Product: D
Version: D2
Hardware: All
OS: All
Status: NEW
On Saturday, 6 February 2016 at 22:51:45 UTC, cy wrote:
auto e = somethingThatFails()
scope(failure) cleanup(e);
makes more sense to me, since it's blatantly obvious that the
construction (and entering) process isn't covered by the
cleanup routine.
Not sure what you mean by that.
There is a frequently ignored technique to profiting with CPA
offers. Notwithstanding costly pay per click, and debilitating
article advertising, there is a superior more viable approach to
get movement and create deals. Partner advertisers might need to
consider CPA email promoting. This
On Sunday, 7 February 2016 at 07:31:51 UTC, tsbockman wrote:
On Sunday, 7 February 2016 at 07:00:04 UTC, Saurabh Das wrote:
On Sunday, 7 February 2016 at 03:16:48 UTC, tsbockman wrote:
(If we go with Saurabh Das' approach, we'll deprecate the old
slice() by ref method, so it there won't be any
https://issues.dlang.org/show_bug.cgi?id=15629
--- Comment #3 from Kenji Hara ---
Dustmited case code:
void main()
{
int[] a = [3];
int value = abs(a[0]);
assert(a[0] == 3);
writeln(value, " ", a);
}
Num abs(Num)(Num x)
{
return x >= 0 ? x : -x;
}
See https://github.com/BBasile/Coedit/releases/tag/2_rc1
Is it hard to make pointee data mutable?
E.g. if have:
--
struct RCString
{
private char[] data;
private @mutable int* counter;
}
--
So for optimiser (in case of immutable) this looks like
--
struct RCString
{
private char[] data;
private @mutable void* counter; //
On Sunday, 7 February 2016 at 12:55:30 UTC, Whirlpool wrote:
Is it the same kind of problem as before ? If my understanding
is correct [1], I need to link with the OpenGL DLL, don't I ? I
found that I have an opengl32.dll file in C:\Windows\System32,
and tried adding the path to it in the
On 07/02/16 11:22 PM, Wobbles wrote:
Just curious, is there a backup plan for D if github.com goes by the
wayside?
Now that there seems to be community back-lash against it (at least on
reddit) maybe a contingency plan would be useful.
Obviously not today or tomorrow, but you never know what's
On Sunday, 7 February 2016 at 10:22:35 UTC, Wobbles wrote:
Just curious, is there a backup plan for D if github.com goes
by the wayside?
Now that there seems to be community back-lash against it (at
least on reddit) maybe a contingency plan would be useful.
Obviously not today or tomorrow,
On Sunday, 7 February 2016 at 14:04:49 UTC, Mike Parker wrote:
Another point to make is that if you need deprecated functions,
DerelictGL3 is not what you want. You should import
derelict.opengl3.gl and use DerelictGL.load/reload instead. It
includes all of the deprecated functions. Just
On Sunday, 7 February 2016 at 05:18:39 UTC, Steven Schveighoffer
wrote:
4 testexpansion 0x00010fb5dbec pure
@safe void
testexpansion.s!(testexpansion.s!(testexpansion.s!(testexpansion.s!(testexpansion.s!
Why "bad" foo is void?
Is there a better way we should be
On Sunday, 7 February 2016 at 12:28:07 UTC, tsbockman wrote:
That is surprising indeed, but I don't see how fixing it would
solve the Tuple.slice() memory alignment issues.
Why won't a reinterpret cast work?
struct tupleX {
T0 _0;
T1 _1;
}
struct tupleX_slice_1_2 {
T0 _dummy0;
T1 _0
On Sunday, 7 February 2016 at 12:51:07 UTC, Ola Fosheim Grøstad
wrote:
On Sunday, 7 February 2016 at 12:28:07 UTC, tsbockman wrote:
That is surprising indeed, but I don't see how fixing it would
solve the Tuple.slice() memory alignment issues.
Why won't a reinterpret cast work?
struct tupleX
Just curious, is there a backup plan for D if github.com goes by
the wayside?
Now that there seems to be community back-lash against it (at
least on reddit) maybe a contingency plan would be useful.
Obviously not today or tomorrow, but you never know what's down
the road.
Am Sun, 07 Feb 2016 00:48:54 +
schrieb Jason White <54f9byee3...@gmail.com>:
> I see the subject of IO streams brought up here occasionally. The
> general consensus seems to be that we need something better than
> what Phobos provides.
>
> I wrote a library "io" that can work as a
Hi,
Sorry, I have a problem again :)
I tried to compile this example :
http://www.glfw.org/docs/latest/quick.html#quick_example
which required to add derelict-gl3
My code is currently this : http://pastebin.com/A5seZmX6
It compiles without errors, but crashes immediately with again
On 2016-02-06 14:33:57 +, Marc Schütz said:
I don't see why this wouldn't work, if you've in fact covered all combinations.
It works, the problem was that castSwitch returns something and I
didn't "catch" it.
It's similar to how castSwitch is implemented, though the double casts
are
On Sunday, 7 February 2016 at 05:18:39 UTC, Steven Schveighoffer
wrote:
Thoughts?
And no line number. But hey, these are convenience for
youngsters. We real program, who type on the keyboard using our
balls, don't need such distractions.
On Sunday, 7 February 2016 at 08:54:08 UTC, ZombineDev wrote:
Contrary to my expectations, slicing bultin tuples returns a
copy. (http://dpaste.dzfl.pl/fd96b17e735d)
Maybe we need to fix this in the compiler. That way we can
reuse the language feature for std.typecons : Tuple.slice().
That is
The specification doesn't list (non-static) members a valid
template alias parameters:
http://dlang.org/spec/template.html#TemplateAliasParameter
On Sunday, 7 February 2016 at 13:01:14 UTC, tsbockman wrote:
That is essentially what my PR does. But, some people are
unhappy with the thought of a slice's type not matching the
type of the equivalent standard Tuple:
Well, Tuple is flawed by design for more than one reason. IMO it
should be
On Sunday, 7 February 2016 at 14:00:24 UTC, Iakh wrote:
Explanations:
As far as "immutable" transitive:
--
immutable RCString str;
*str.counter++; // Impossible/error/undefined behavior(with const
cast)
--
Language defines immutable to do some optimizations based on true
constness of
On Sunday, 7 February 2016 at 10:27:02 UTC, Rikki Cattermole
wrote:
On 07/02/16 11:22 PM, Wobbles wrote:
Just curious, is there a backup plan for D if github.com goes
by the
wayside?
Now that there seems to be community back-lash against it (at
least on
reddit) maybe a contingency plan
On Saturday, 6 February 2016 at 20:18:57 UTC, Craig Dillabaugh
wrote:
Anyone interested and capable of mentor a student interested in
doing FlatBuffers for D.
I could do that. Currently, as a side project, I'm working on
adding D support for Protocol Buffers v3 [1].
Main goals of the new
On Sunday, 7 February 2016 at 10:48:49 UTC, Joakim wrote:
On Sunday, 7 February 2016 at 10:27:02 UTC, Rikki Cattermole
wrote:
On 07/02/16 11:22 PM, Wobbles wrote:
[...]
The only thing that we have hosted on Github is code.
So excluding integrations, we could move over to Bitbucket
without
On Sunday, 7 February 2016 at 19:43:23 UTC, rsw0x wrote:
On Sunday, 7 February 2016 at 19:39:27 UTC, rsw0x wrote:
On Sunday, 7 February 2016 at 19:27:19 UTC, Charles Hixson
wrote:
If I define a shared ulong variable, is increment an atomic
operation?
E.g.
shared ulong t;
...
t++;
It seems
Dpaste currently does not expire pastes by default. I was thinking it
would be nice if it saved them in the Wayback Machine such that they are
archived redundantly.
I'm not sure what's the way to do it - probably linking the
newly-generated paste URLs from a page that the Wayback Machine
On Sunday, 7 February 2016 at 21:49:24 UTC, Matt Elkins wrote:
I've been experiencing some odd behavior, where it would appear
that a struct's destructor is being called before the object's
lifetime expires. More likely I am misunderstanding something
about the lifetime rules for structs. I
On Sunday, 7 February 2016 at 19:27:19 UTC, Charles Hixson wrote:
If I define a shared ulong variable, is increment an atomic
operation?
E.g.
shared ulong t;
...
t++;
It seems as if it ought to be, but it could be split into read,
increment, store.
I started off defining a shared struct,
https://issues.dlang.org/show_bug.cgi?id=15652
Issue ID: 15652
Summary: Alias this exceptions cannot be caught, but shadow
others
Product: D
Version: D2
Hardware: All
OS: All
Status: NEW
On Sunday, 7 February 2016 at 20:25:44 UTC, Minas Mina wrote:
On Sunday, 7 February 2016 at 19:43:23 UTC, rsw0x wrote:
On Sunday, 7 February 2016 at 19:39:27 UTC, rsw0x wrote:
On Sunday, 7 February 2016 at 19:27:19 UTC, Charles Hixson
wrote:
[...]
I've been experiencing some odd behavior, where it would appear
that a struct's destructor is being called before the object's
lifetime expires. More likely I am misunderstanding something
about the lifetime rules for structs. I haven't been able to
reproduce with a particularly minimal
On Monday, 25 January 2016 at 22:06:31 UTC, Era Scarecrow wrote:
On Monday, 25 January 2016 at 21:22:13 UTC, Joseph Rushton
Wakeling wrote:
I have been wondering about how allocators could help to deal
with these problems. Could you put forward a minimal example
of how you would see it
On Sunday, 7 February 2016 at 22:35:57 UTC, anonymous wrote:
On 07.02.2016 23:07, Márcio Martins wrote:
The destructor you are seeing is from the assignment:
m_tileView = TileView(...);
This creates a temporary TileView, copies it to m_tileView,
and then
destroys it. I suppose you want to
On Sunday, 7 February 2016 at 19:39:27 UTC, rsw0x wrote:
On Sunday, 7 February 2016 at 19:27:19 UTC, Charles Hixson
wrote:
If I define a shared ulong variable, is increment an atomic
operation?
E.g.
shared ulong t;
...
t++;
It seems as if it ought to be, but it could be split into
read,
On Sunday, 7 February 2016 at 18:46:48 UTC, Nick Sabalausky wrote:
I was just updating a project's .travis.yml file and noticed:
It doesn't seem we have any one-stop-shop location to check all
the versions of DMD/LDC/GDC currently available on travis-ci.
It's be really nice if we had some
Thank you very much for your explanations and patience :) I
indeed have an AMD Radeon HD 7870 card, and using 4.4 as the max
version fixes my problem !
On 07.02.2016 22:49, Matt Elkins wrote:
From this non-reduced situation, does anything jump out? Am I missing
something about struct lifetimes? This is the only place I instantiate a
TileView.
Looks weird. I presume this doesn't happen with simpler constructor
parameters/arguments, like int
On 07.02.2016 23:07, Márcio Martins wrote:
The destructor you are seeing is from the assignment:
m_tileView = TileView(...);
This creates a temporary TileView, copies it to m_tileView, and then
destroys it. I suppose you want to move it instead. You need to copy the
handles from the temporary
https://issues.dlang.org/show_bug.cgi?id=15653
Issue ID: 15653
Summary: IFTI fails for immutable parameter
Product: D
Version: D2
Hardware: All
OS: All
Status: NEW
Severity: major
Priority: P1
On Sunday, 7 February 2016 at 22:04:27 UTC, anonymous wrote:
On 07.02.2016 22:49, Matt Elkins wrote:
From this non-reduced situation, does anything jump out? Am I
missing
something about struct lifetimes? This is the only place I
instantiate a
TileView.
Looks weird. I presume this doesn't
On Sunday, 7 February 2016 at 13:13:21 UTC, Ola Fosheim Grøstad
wrote:
On Sunday, 7 February 2016 at 13:01:14 UTC, tsbockman wrote:
That is essentially what my PR does. But, some people are
unhappy with the thought of a slice's type not matching the
type of the equivalent standard Tuple:
On 02/07/2016 05:48 AM, Joakim wrote:
Unfortunately, there's a lot of valuable info in the PR comments, that
would be lost if github.com went down. Since D never switched from
bugzilla to github for bugs, that wouldn't be an issue. Hopefully, we
could pull that github PR discussion from a
On Sunday, 7 February 2016 at 16:27:32 UTC, Saurabh Das wrote:
Why is the design flawed?
Because it breaks expectations.
Tuples should be builtin and the primarily use case is supporting
multiple return values with heavy duty register optimization.
I was just updating a project's .travis.yml file and noticed: It doesn't
seem we have any one-stop-shop location to check all the versions of
DMD/LDC/GDC currently available on travis-ci.
It's be really nice if we had some auto-updated chart like that which
ALSO listed the DMDFE, LLVM and GCC
If I define a shared ulong variable, is increment an atomic operation?
E.g.
shared ulong t;
...
t++;
It seems as if it ought to be, but it could be split into read,
increment, store.
I started off defining a shared struct, but that seems silly, as if the
operations defined within a shared
On 07.02.2016 23:49, Matt Elkins wrote:
Oi. Yes, I can, but it is quite a lot of code even if you don't count
that it is dependent on OpenGL, GLFW, and gl3n to run to this point.
This is why I was disappointed that simpler reproducing cases weren't
appearing. I should probably spend more time
On 02/04/2016 09:46 PM, Tofu Ninja wrote:
On Thursday, 4 February 2016 at 15:33:41 UTC, Andrei Alexandrescu wrote:
https://github.com/D-Programming-Language/phobos/pull/3971 -- Andrei
People one github were asking for a dump function so they could do
int a = 5;
dump!("a"); //
On Sunday, 7 February 2016 at 16:49:16 UTC, Ola Fosheim Grøstad
wrote:
On Sunday, 7 February 2016 at 16:27:32 UTC, Saurabh Das wrote:
Why is the design flawed?
Because it breaks expectations.
Tuples should be builtin and the primarily use case is
supporting multiple return values with heavy
On Sunday, 7 February 2016 at 23:11:34 UTC, anonymous wrote:
On 07.02.2016 23:49, Matt Elkins wrote:
Oi. Yes, I can, but it is quite a lot of code even if you
don't count
that it is dependent on OpenGL, GLFW, and gl3n to run to this
point.
This is why I was disappointed that simpler
Some environment information:
DMD 2.070 32-bit
Windows 7 (64-bit)
On Sunday, 7 February 2016 at 23:26:05 UTC, Andrei Alexandrescu
wrote:
On 02/04/2016 09:46 PM, Tofu Ninja wrote:
On Thursday, 4 February 2016 at 15:33:41 UTC, Andrei
Alexandrescu wrote:
https://github.com/D-Programming-Language/phobos/pull/3971 --
Andrei
People one github were asking for a
Right now I'm using a logical ||:
if (!(2*PI - EPS!float <= t1-t0 || t1-t0 <= 2*PI + EPS!float)) {
But I'll be doing this a lot, so was wondering if there's a D
native way of doing it.
Thanks.
https://issues.dlang.org/show_bug.cgi?id=15376
Jonathan M Davis changed:
What|Removed |Added
Status|NEW |RESOLVED
On Sunday, 7 February 2016 at 21:26:36 UTC, Xinok wrote:
On Sunday, 7 February 2016 at 18:46:48 UTC, Nick Sabalausky
wrote:
I was just updating a project's .travis.yml file and noticed:
It doesn't seem we have any one-stop-shop location to check
all the versions of DMD/LDC/GDC currently
On 2/7/16 10:42 AM, Iakh wrote:
On Sunday, 7 February 2016 at 05:18:39 UTC, Steven Schveighoffer wrote:
4 testexpansion 0x00010fb5dbec pure @safe
void
testexpansion.s!(testexpansion.s!(testexpansion.s!(testexpansion.s!(testexpansion.s!
Why "bad" foo is void?
Thanks, that's what I needed to know.
I'm still going to do it as a class, but now only the inc routine needs
to be handled specially.
(The class is so that other places where the value is used don't even
need to know that it's special. And so that instances are easy to share
between
https://issues.dlang.org/show_bug.cgi?id=15655
Issue ID: 15655
Summary: SysTime.from*String incorrectly accept single digit
time zones and minutes > 59
Product: D
Version: D2
Hardware: All
OS: All
On Sunday, 7 February 2016 at 22:27:40 UTC, Joseph Rushton
Wakeling wrote:
On Monday, 25 January 2016 at 22:06:31 UTC, Era Scarecrow wrote:
What you describe makes sense, but I don't quite follow what
you mean in one particular case:
Technically alloca simply returns the current sp, then
On Sunday, 7 February 2016 at 10:50:24 UTC, Johannes Pfau wrote:
I saw this on code.dlang.org some time ago and had a quick
look. First of all this would have to go into phobos to make
sure it's used as some kind of a standard. Conflicting stream
libraries would only cause more trouble.
Then
On 2/7/16 5:20 AM, deadalnix wrote:
On Sunday, 7 February 2016 at 05:18:39 UTC, Steven Schveighoffer wrote:
Thoughts?
And no line number. But hey, these are convenience for youngsters. We
real program, who type on the keyboard using our balls, don't need such
distractions.
Remind me never
https://issues.dlang.org/show_bug.cgi?id=15654
Issue ID: 15654
Summary: SysTime.toISOString formats the time zones incorrectly
Product: D
Version: D2
Hardware: All
OS: All
Status: NEW
Severity: normal
On Monday, 8 February 2016 at 02:47:24 UTC, Enjoys Math wrote:
Right now I'm using a logical ||:
if (!(2*PI - EPS!float <= t1-t0 || t1-t0 <= 2*PI + EPS!float)) {
But I'll be doing this a lot, so was wondering if there's a D
native way of doing it.
Thanks.
Currently I have:
@property T
On Monday, 8 February 2016 at 03:09:53 UTC, Enjoys Math wrote:
was wondering if there's a D
native way of doing it.
That is the D native way of doing it, but you could clean up a
lot of the boilerplate with some more templates. Also, || tests
for exclusion, as in whether something is NOT in
On Monday, 8 February 2016 at 01:48:32 UTC, Steven Schveighoffer
wrote:
On 2/7/16 10:42 AM, Iakh wrote:
On Sunday, 7 February 2016 at 05:18:39 UTC, Steven
Schveighoffer wrote:
4 testexpansion 0x00010fb5dbec
pure @safe
void
I have several class members:
Arc[4] arcs;
Arc[4] arcs_2;
and Id like to initialize them with the same function, so how do
I "pass them in" by reference?
On Monday, 8 February 2016 at 05:59:43 UTC, Enjoys Math wrote:
I have several class members:
Arc[4] arcs;
Arc[4] arcs_2;
and Id like to initialize them with the same function, so how
do I "pass them in" by reference?
void foo(ref Arc[4] arr)
{
…
}
The dimension can of course be
On Monday, 8 February 2016 at 06:01:24 UTC, Jakob Ovrum wrote:
On Monday, 8 February 2016 at 05:59:43 UTC, Enjoys Math wrote:
I have several class members:
Arc[4] arcs;
Arc[4] arcs_2;
and Id like to initialize them with the same function, so how
do I "pass them in" by reference?
void
On Sunday, 7 February 2016 at 13:18:44 UTC, Basile Burg wrote:
See https://github.com/BBasile/Coedit/releases/tag/2_rc1
Cool! Thanks! But do you have any plans to reimplement it from
Pascal to В to get it's more native...
https://github.com/filcuc/DOtherSide maybe helpful
On Saturday, 6 February 2016 at 23:35:17 UTC, Ali Çehreli wrote:
On 02/06/2016 10:05 AM, Voitech wrote:
> [...]
You can use string mixins (makeCtor and makeCtors):
string makeCtor(T)() {
import std.string : format;
[...]
Thank you very much for answering.
Cheers
76 matches
Mail list logo