On 10/9/15 10:37 PM, Adam D. Ruppe wrote:
On Saturday, 10 October 2015 at 02:31:51 UTC, Martin Nowak wrote:
nothing to warrant the invasive language feature @property is.
There's no reason for @property to be invasive. ALL it needs to do is
handle that one case, it shouldn't even be used anywh
On Tuesday, 13 October 2015 at 16:07:50 UTC, Kagamin wrote:
What doesn't work for you?
extern int f();
struct T(F){}
T!f t; //Error: template instance T!(f) does not match template
declaration T(F)
struct A(alias F){}
A!f a; //works
I don't remember. I fixed the issues a few weeks ago using
On 14.10.2015 15:26, Szymon Gatner wrote:
To get compatible class layout, the D compiler has to omit it's class
info entry in the vtable of C++ classes. In addition D doesn't know
about C++ RTTI (I don't know if this is planned to add), so it cannot
do the dynamic cast from Operation to Subtra
On Wednesday, 14 October 2015 at 13:12:00 UTC, Rainer Schuetze
wrote:
On 14.10.2015 14:57, Szymon Gatner wrote:
extern(C++)
void freeSubtract(Operation animal) {
auto cat = cast(Subtract) animal; <<== cast yields null
if(cat !is null) {
destroy(cat);
free(cast(void*) cat);
On 14.10.2015 14:57, Szymon Gatner wrote:
extern(C++)
void freeSubtract(Operation animal) {
auto cat = cast(Subtract) animal; <<== cast yields null
if(cat !is null) {
destroy(cat);
free(cast(void*) cat);
}
}
extern(C++)
void useOperation(Operation t) {
auto res = t.ex
On Wednesday, 14 October 2015 at 12:39:46 UTC, Rainer Schuetze
wrote:
As Szymon noticed, you can compile an empty main into the
static D library. The additional C main that is generated by
DMD won't cause ambiguities as long as your C main is not also
in a static library.
Thanks for the adv
On Wednesday, 14 October 2015 at 11:54:22 UTC, Szymon Gatner
wrote:
On Wednesday, 14 October 2015 at 11:46:27 UTC, ZombineDev wrote:
2) How can I workaround the problem that _minfo* and _deh* are
not generated because my main is in C++?
Just add a file with int main() in D library to fix th
On Wednesday, 14 October 2015 at 12:35:30 UTC, Rainer Schuetze
wrote:
I just noticed that the magic symbol translation _snprintf ->
__snprintf isn't included without linking the internal function
init_msvc (which is normally done by d_run_main which is called
by the generated C main).
The c
On 14.10.2015 13:39, Szymon Gatner wrote:
On Tuesday, 13 October 2015 at 20:10:22 UTC, Rainer Schuetze wrote:
On 13.10.2015 21:44, ZombineDev wrote:
[...]
The library issues are the same for 32-bit and 64-bit.
[...]
Yes, but there is some magic involved when linking against the VS2015
On 14.10.2015 13:46, ZombineDev wrote:
On Tuesday, 13 October 2015 at 20:10:22 UTC, Rainer Schuetze wrote:
Yes, but there is some magic involved when linking against the VS2015
CRT. To use symbols like snprintf and sscanf, you must also pass
legacy_stdio_definitions.lib to the linker, which is
On Wednesday, 14 October 2015 at 12:05:28 UTC, Szymon Gatner
wrote:
On Wednesday, 14 October 2015 at 11:39:26 UTC, Szymon Gatner
wrote:
On Tuesday, 13 October 2015 at 20:10:22 UTC, Rainer Schuetze
wrote:
[...]
I am trying (as with every new release ;)) to link static D
library to existing C+
On Wednesday, 14 October 2015 at 11:39:26 UTC, Szymon Gatner
wrote:
On Tuesday, 13 October 2015 at 20:10:22 UTC, Rainer Schuetze
wrote:
[...]
I am trying (as with every new release ;)) to link static D
library to existing C++ project and I am having same issue:
Error 2 error LNK2019: unreso
On Wednesday, 14 October 2015 at 11:46:27 UTC, ZombineDev wrote:
2) How can I workaround the problem that _minfo* and _deh* are
not generated because my main is in C++?
Just add a file with int main() in D library to fix this.
On Tuesday, 13 October 2015 at 20:10:22 UTC, Rainer Schuetze
wrote:
Yes, but there is some magic involved when linking against the
VS2015 CRT. To use symbols like snprintf and sscanf, you must
also pass legacy_stdio_definitions.lib to the linker, which is
done automatically if you use dmd as a
On Tuesday, 13 October 2015 at 20:10:22 UTC, Rainer Schuetze
wrote:
On 13.10.2015 21:44, ZombineDev wrote:
[...]
The library issues are the same for 32-bit and 64-bit.
[...]
Yes, but there is some magic involved when linking against the
VS2015 CRT. To use symbols like snprintf and sscan
On 13.10.2015 21:44, ZombineDev wrote:
On Tuesday, 13 October 2015 at 19:17:27 UTC, ZombineDev wrote:
On Tuesday, 13 October 2015 at 19:14:51 UTC, ZombineDev wrote:
[...]
Is the problem related to the new CRT in VS2015? Previously I thought
that the problem is 64-bit only, but it seams like
On Tuesday, 13 October 2015 at 19:17:27 UTC, ZombineDev wrote:
On Tuesday, 13 October 2015 at 19:14:51 UTC, ZombineDev wrote:
[...]
Is the problem related to the new CRT in VS2015? Previously I
thought that the problem is 64-bit only, but it seams like it is
for both 32-bit and 64-bit MSCOFF.
On Tuesday, 13 October 2015 at 19:14:51 UTC, ZombineDev wrote:
On Wednesday, 7 October 2015 at 22:33:09 UTC, Martin Nowak
wrote:
First beta for the 2.069.0 release.
http://dlang.org/download.html#dmd_beta
http://dlang.org/changelog/2.069.0.html
Please report any bugs at https://issues.dlang.
On Wednesday, 7 October 2015 at 22:33:09 UTC, Martin Nowak wrote:
First beta for the 2.069.0 release.
http://dlang.org/download.html#dmd_beta
http://dlang.org/changelog/2.069.0.html
Please report any bugs at https://issues.dlang.org
-Martin
I decided to try the newly included mscoff 32 Pho
On Tuesday, 13 October 2015 at 13:57:15 UTC, Meta wrote:
On Tuesday, 13 October 2015 at 13:18:36 UTC, Kagamin wrote:
Well, in order to pass the result of a function call to a
template parameter means that the function must be evaluated
at compile time, which is not always possible, so it probab
On Tuesday, 13 October 2015 at 13:18:36 UTC, Kagamin wrote:
Well, in order to pass the result of a function call to a
template parameter means that the function must be evaluated at
compile time, which is not always possible, so it probably
doesn't make sense to call a function when passed as a
On Sunday, 11 October 2015 at 09:54:04 UTC, Jacob Carlborg wrote:
That would be me :) [1]. I think the biggest issue was that
something that worked before stopped working, because a field
was changed to a method and the method returned a function
pointer.
[1]
http://forum.dlang.org/thread/ka
On Saturday, 10 October 2015 at 02:57:03 UTC, Meta wrote:
I don't know how much metaprogramming-heavy generic code you've
written, but I can say from first-hand experience that there is
such a thing as Hell, and it is called Optional Parens.
Jokes aside, I've finally fixed (read: worked around
On Wednesday, 7 October 2015 at 22:33:09 UTC, Martin Nowak wrote:
First beta for the 2.069.0 release.
http://dlang.org/download.html#dmd_beta
http://dlang.org/changelog/2.069.0.html
Please report any bugs at https://issues.dlang.org
-Martin
brew reinstall dmd --devel
:) thanks for all the
On Sunday, 11 October 2015 at 17:57:54 UTC, Meta wrote:
Just a joke; I consider this a terrible aspect of D.
:) I never know what is a joke or not in the forums these days.
Anyway, a key difference is that a key inspiration for both BETA
and also the actor model is modelling physical (or ima
On Sunday, 11 October 2015 at 17:27:39 UTC, Ola Fosheim Grøstad
wrote:
On Sunday, 11 October 2015 at 16:42:36 UTC, Meta wrote:
On Sunday, 11 October 2015 at 16:00:40 UTC, Ola Fosheim
Grøstad wrote:
That also means that BETA does not distinguish between a
function call and an assignment.
Hey,
On Sunday, 11 October 2015 at 16:42:36 UTC, Meta wrote:
On Sunday, 11 October 2015 at 16:00:40 UTC, Ola Fosheim Grøstad
wrote:
That also means that BETA does not distinguish between a
function call and an assignment.
Hey, neither does D!
writeln("Hello, World!");
writeln = "Hello, World!";
On Sunday, 11 October 2015 at 16:00:40 UTC, Ola Fosheim Grøstad
wrote:
That also means that BETA does not distinguish between a
function call and an assignment.
Hey, neither does D!
writeln("Hello, World!");
writeln = "Hello, World!";
On Sunday, 11 October 2015 at 01:52:12 UTC, deadalnix wrote:
On Saturday, 10 October 2015 at 16:31:27 UTC, Ola Fosheim
Grøstad wrote:
On Saturday, 10 October 2015 at 12:51:43 UTC, Jacob Carlborg
wrote:
In Ruby, no one will ever use empty parentheses for calling a
method.
That's actually the s
On 2015-10-11 11:45, Johannes Pfau wrote:
We even have such a problem in object.d:
https://github.com/D-Programming-Language/druntime/blob/master/src/object.d#L1461
I remember somebody asking in D.learn why his custom test runner did
not work. Problem was related to wrong parenthesis: The user
Am Sun, 11 Oct 2015 01:54:39 +
schrieb deadalnix :
> On Saturday, 10 October 2015 at 02:57:03 UTC, Meta wrote:
> > On Saturday, 10 October 2015 at 02:31:51 UTC, Martin Nowak
> > wrote:
> >> That's what I meant, weird use-case, at best it's a callback
> >> better/setter.
> >> I've never writt
On Wednesday, 7 October 2015 at 22:33:09 UTC, Martin Nowak wrote:
First beta for the 2.069.0 release.
http://dlang.org/download.html#dmd_beta
http://dlang.org/changelog/2.069.0.html
Please report any bugs at https://issues.dlang.org
-Martin
First beta, so far I can use it as a drop in repl
On Saturday, 10 October 2015 at 16:31:27 UTC, Ola Fosheim Grøstad
wrote:
On Saturday, 10 October 2015 at 12:51:43 UTC, Jacob Carlborg
wrote:
In Ruby, no one will ever use empty parentheses for calling a
method.
That's actually the same as Simula. Functions/procedures with
no parameters is cal
On Saturday, 10 October 2015 at 02:57:03 UTC, Meta wrote:
On Saturday, 10 October 2015 at 02:31:51 UTC, Martin Nowak
wrote:
That's what I meant, weird use-case, at best it's a callback
better/setter.
I've never written such code, but even if you would, the 2
pairs of parens are only a tiny prob
On Saturday, 10 October 2015 at 01:52:36 UTC, Martin Nowak wrote:
Right, ideally a @proptery function can perfectly replace a
variable, but practically calling the return value seems far
fetched.
What would you use that for, a handwritten interface struct
with function pointers made read-only u
On Saturday, October 10, 2015 02:57:01 Meta via Digitalmars-d-announce wrote:
> On Saturday, 10 October 2015 at 02:31:51 UTC, Martin Nowak wrote:
> > That's what I meant, weird use-case, at best it's a callback
> > better/setter.
> > I've never written such code, but even if you would, the 2
> > pa
On Saturday, 10 October 2015 at 12:51:43 UTC, Jacob Carlborg
wrote:
In Ruby, no one will ever use empty parentheses for calling a
method.
That's actually the same as Simula. Functions/procedures with no
parameters is called without parentheses.
On 10 October 2015 at 14:51, Jacob Carlborg via Digitalmars-d-announce <
digitalmars-d-announce@puremagic.com> wrote:
> On 2015-10-10 03:52, Martin Nowak wrote:
>
> Scala and Ruby seem to do well with sloppy parens.
>>
>
> A few notes about why Ruby doesn't have the same problems as D has:
>
> 1.
On 2015-10-10 03:52, Martin Nowak wrote:
Scala and Ruby seem to do well with sloppy parens.
A few notes about why Ruby doesn't have the same problems as D has:
1. Ruby has optional parentheses for all method calls, regardless if
they accept arguments or not
2. Ruby has a different syntax f
On Saturday, 10 October 2015 at 01:52:36 UTC, Martin Nowak wrote:
To me the whole property discussion looks like one of those
endless debates about an insignificant detail.
Scala and Ruby seem to do well with sloppy parens.
Strict typing and explicitness has a real effect on code
legibility a
On Saturday, 10 October 2015 at 02:31:51 UTC, Martin Nowak wrote:
That's what I meant, weird use-case, at best it's a callback
better/setter.
I've never written such code, but even if you would, the 2
pairs of parens are only a tiny problem for generic code,
nothing to warrant the invasive lang
On Saturday, 10 October 2015 at 02:31:51 UTC, Martin Nowak wrote:
nothing to warrant the invasive language feature @property is.
There's no reason for @property to be invasive. ALL it needs to
do is handle that one case, it shouldn't even be used anywhere
else. Everything else is trivial or i
On Saturday, 10 October 2015 at 02:15:14 UTC, Adam D. Ruppe wrote:
On Saturday, 10 October 2015 at 01:52:36 UTC, Martin Nowak
wrote:
What would you use that for, a handwritten interface struct
with function pointers made read-only using @property?
var a = var.emptyObject; // works today
a.prop
On Saturday, 10 October 2015 at 01:52:36 UTC, Martin Nowak wrote:
What would you use that for, a handwritten interface struct
with function pointers made read-only using @property?
var a = var.emptyObject; // works today
a.prop = { do_stuff; }; // works today
a.prop(); // useless no op
a.prop()
On Saturday, 10 October 2015 at 01:27:09 UTC, Jonathan M Davis
wrote:
Regardless, what we pretty much need to do with @property at
some point is make is that it's used to make it so that a
single pair of parens operate on the return value rather than
the function even if we don't do anything el
On Thursday, October 08, 2015 15:00:15 Martin Nowak via Digitalmars-d-announce
wrote:
> On Thursday, 8 October 2015 at 12:48:48 UTC, Adam D. Ruppe wrote:
> > On Thursday, 8 October 2015 at 04:14:59 UTC, extrawurst wrote:
> >> Does that mean @property has no effect anymore ?
> >
> > @property never
On Thursday, 8 October 2015 at 07:25:36 UTC, Andrea Fontana wrote:
On Thursday, 8 October 2015 at 04:14:59 UTC, extrawurst wrote:
On Wednesday, 7 October 2015 at 22:33:09 UTC, Martin Nowak
wrote:
[...]
`The -property switch has been deprecated.` Does that mean
@property has no effect anymore
On Friday, 9 October 2015 at 09:32:05 UTC, Joakim wrote:
downloads much? Maybe you should add a warning there, for
those who may not know the meaning of a beta.
If you're a coder you know what it means.
If you just started with programming probably it doesn't make any
difference :)
On Wednesday, 7 October 2015 at 22:33:09 UTC, Martin Nowak wrote:
First beta for the 2.069.0 release.
http://dlang.org/download.html#dmd_beta
http://dlang.org/changelog/2.069.0.html
Please report any bugs at https://issues.dlang.org
-Martin
I just noticed that you added the beta to the mai
On Thursday, 8 October 2015 at 12:32:59 UTC, John Colvin wrote:
On Wednesday, 7 October 2015 at 22:33:09 UTC, Martin Nowak
wrote:
First beta for the 2.069.0 release.
http://dlang.org/download.html#dmd_beta
http://dlang.org/changelog/2.069.0.html
Please report any bugs at https://issues.dlang
On Thursday, 8 October 2015 at 15:04:08 UTC, David Nadlinger
wrote:
On Thursday, 8 October 2015 at 15:01:31 UTC, Martin Nowak wrote:
On Thursday, 8 October 2015 at 12:20:23 UTC, Andrea Fontana
wrote:
Are dmd 2.069b1 binaries compiled with dmd 2.069b1 or with
dmd 2.068.2?
The last released com
On Thursday, 8 October 2015 at 20:59:57 UTC, NVolcz wrote:
The changelog links to:
http://dlang.org/phobos/std_experimental_allocator.html
which returns 404 for me.
I remember seeing discussions about versioning the docs. What
happened to that?
Fixed by now.
On 10/8/15 4:59 PM, NVolcz wrote:
On Wednesday, 7 October 2015 at 22:33:09 UTC, Martin Nowak wrote:
First beta for the 2.069.0 release.
http://dlang.org/download.html#dmd_beta
http://dlang.org/changelog/2.069.0.html
Please report any bugs at https://issues.dlang.org
-Martin
The changelog li
On Thursday, 8 October 2015 at 16:12:52 UTC, ponce wrote:
On Wednesday, 7 October 2015 at 22:33:09 UTC, Martin Nowak
wrote:
First beta for the 2.069.0 release.
Weren't there codegen improvements in DMD?
https://github.com/D-Programming-Language/dlang.org/pull/1121
On Wednesday, 7 October 2015 at 22:33:09 UTC, Martin Nowak wrote:
First beta for the 2.069.0 release.
http://dlang.org/download.html#dmd_beta
http://dlang.org/changelog/2.069.0.html
Please report any bugs at https://issues.dlang.org
-Martin
The changelog links to:
http://dlang.org/phobos/s
On 10/07/2015 06:33 PM, Martin Nowak wrote:
First beta for the 2.069.0 release.
http://dlang.org/download.html#dmd_beta
http://dlang.org/changelog/2.069.0.html
Please report any bugs at https://issues.dlang.org
-Martin
Can we please get this one in?:
https://github.com/D-Programming-Langua
On Wednesday, 7 October 2015 at 22:33:09 UTC, Martin Nowak wrote:
First beta for the 2.069.0 release.
Weren't there codegen improvements in DMD?
On Thursday, 8 October 2015 at 04:14:59 UTC, extrawurst wrote:
On Wednesday, 7 October 2015 at 22:33:09 UTC, Martin Nowak
wrote:
First beta for the 2.069.0 release.
http://dlang.org/download.html#dmd_beta
http://dlang.org/changelog/2.069.0.html
Please report any bugs at https://issues.dlang.
On Thursday 08 October 2015 16:34, anonymous wrote:
> On Thursday 08 October 2015 06:14, extrawurst wrote:
>
>> `The -property switch has been deprecated.` Does that mean
>> @property has no effect anymore ?
>
> Yes.
Correction: @property has at least one effect without -property. typeof acts
On Thursday, 8 October 2015 at 14:59:15 UTC, Jack Stouffer wrote:
I think it should be mentioned in the change log the
substantial improvements that were made to the docs since last
release. After over 30 PRs were merged for improving the docs,
they are WAY better than the 2.068 docs.
Sure, j
On Thursday, 8 October 2015 at 12:48:48 UTC, Adam D. Ruppe wrote:
On Thursday, 8 October 2015 at 04:14:59 UTC, extrawurst wrote:
Does that mean @property has no effect anymore ?
@property never actually worked anyway. It is still my hope
that it will be correctly implemented some day though
On Thursday, 8 October 2015 at 12:20:23 UTC, Andrea Fontana wrote:
Are dmd 2.069b1 binaries compiled with dmd 2.069b1 or with dmd
2.068.2?
The last released compiler, we don't have any bootstrap method
(using a small C++ compiler or so).
On Thursday, 8 October 2015 at 15:01:31 UTC, Martin Nowak wrote:
On Thursday, 8 October 2015 at 12:20:23 UTC, Andrea Fontana
wrote:
Are dmd 2.069b1 binaries compiled with dmd 2.069b1 or with dmd
2.068.2?
The last released compiler, we don't have any bootstrap method
(using a small C++ compile
On Wednesday, 7 October 2015 at 22:33:09 UTC, Martin Nowak wrote:
First beta for the 2.069.0 release.
http://dlang.org/download.html#dmd_beta
http://dlang.org/changelog/2.069.0.html
Please report any bugs at https://issues.dlang.org
-Martin
I think it should be mentioned in the change log
On Thursday 08 October 2015 06:14, extrawurst wrote:
> `The -property switch has been deprecated.` Does that mean
> @property has no effect anymore ?
Yes. I've made a pull request to mention that (and put a note on the spec
page).
https://github.com/D-Programming-Language/dlang.org/pull/1119
On Thursday, 8 October 2015 at 09:36:31 UTC, lobo wrote:
PS: Big thanks for the much improved release process that you
guys are maintaining.
I agree. Thank you, Martin.
On Thursday, 8 October 2015 at 04:14:59 UTC, extrawurst wrote:
Does that mean @property has no effect anymore ?
@property never actually worked anyway. It is still my hope that
it will be correctly implemented some day though - the hard
problem it was meant to solve is still there (returning
On Wednesday, 7 October 2015 at 22:33:09 UTC, Martin Nowak wrote:
First beta for the 2.069.0 release.
http://dlang.org/download.html#dmd_beta
http://dlang.org/changelog/2.069.0.html
Please report any bugs at https://issues.dlang.org
-Martin
Am I being dumb or does SYSCONFDIR do absolutely
On Thursday, 8 October 2015 at 09:17:16 UTC, Martin Nowak wrote:
On Thursday, 8 October 2015 at 04:53:53 UTC, Suliman wrote:
Is it DDMD based release?
Yes.
Are dmd 2.069b1 binaries compiled with dmd 2.069b1 or with dmd
2.068.2?
On 10/08/2015 11:36 AM, lobo wrote:
>
> Is there any info on the benchmarking between DDMD and DMD?
Still on the todo list to decide whether we need to use gdc to build ddmd.
https://trello.com/c/OT6jlFNa/85-rebench-ddmd-vs-dmd-compiler-speed
On Thursday, 8 October 2015 at 09:17:16 UTC, Martin Nowak wrote:
On Thursday, 8 October 2015 at 04:53:53 UTC, Suliman wrote:
Is it DDMD based release?
Yes.
Is there any info on the benchmarking between DDMD and DMD?
bye,
lobo
PS: Big thanks for the much improved release process that you
g
On Wednesday, 7 October 2015 at 22:33:09 UTC, Martin Nowak wrote:
First beta for the 2.069.0 release.
http://dlang.org/download.html#dmd_beta
http://dlang.org/changelog/2.069.0.html
Please report any bugs at https://issues.dlang.org
-Martin
Thanks!
Please add the PR about allocators for t
On Thursday, 8 October 2015 at 04:53:53 UTC, Suliman wrote:
Is it DDMD based release?
Yes.
On Wednesday, 7 October 2015 at 22:33:09 UTC, Martin Nowak wrote:
First beta for the 2.069.0 release.
http://dlang.org/download.html#dmd_beta
http://dlang.org/changelog/2.069.0.html
Please report any bugs at https://issues.dlang.org
-Martin
Got an issue:
https://issues.dlang.org/show_bug.c
On Wednesday, 7 October 2015 at 22:33:09 UTC, Martin Nowak wrote:
First beta for the 2.069.0 release.
http://dlang.org/download.html#dmd_beta
http://dlang.org/changelog/2.069.0.html
Please report any bugs at https://issues.dlang.org
-Martin
The "libcurl is now loaded dynamically" link is b
On Thursday, 8 October 2015 at 04:14:59 UTC, extrawurst wrote:
On Wednesday, 7 October 2015 at 22:33:09 UTC, Martin Nowak
wrote:
First beta for the 2.069.0 release.
http://dlang.org/download.html#dmd_beta
http://dlang.org/changelog/2.069.0.html
Please report any bugs at https://issues.dlang.
08.10.2015 01:33, Martin Nowak пишет:
First beta for the 2.069.0 release.
http://dlang.org/download.html#dmd_beta
http://dlang.org/changelog/2.069.0.html
Please report any bugs at https://issues.dlang.org
-Martin
Cool!
References to `cmp`, `std.experimental.allocator` reference to current
On Wednesday, 7 October 2015 at 22:33:09 UTC, Martin Nowak wrote:
First beta for the 2.069.0 release.
http://dlang.org/download.html#dmd_beta
http://dlang.org/changelog/2.069.0.html
Please report any bugs at https://issues.dlang.org
-Martin
Is it DDMD based release?
On Wednesday, 7 October 2015 at 22:33:09 UTC, Martin Nowak wrote:
First beta for the 2.069.0 release.
http://dlang.org/download.html#dmd_beta
http://dlang.org/changelog/2.069.0.html
Please report any bugs at https://issues.dlang.org
-Martin
`The -property switch has been deprecated.` Does
First beta for the 2.069.0 release.
http://dlang.org/download.html#dmd_beta
http://dlang.org/changelog/2.069.0.html
Please report any bugs at https://issues.dlang.org
-Martin
80 matches
Mail list logo