On Friday, 29 August 2014 at 02:38:54 UTC, H. S. Teoh via
Digitalmars-d wrote:
Maybe a more relevant question might be, is there any existing
code that
*isn't* broken by structs not being destructed? (D-structed,
har har.)
Well, this new change *could* greatly increase the amount of
"allocati
Scott Wilson:
I found https://github.com/acmeism/RosettaCodeData. Is it fresh?
The most recently update is 5 months ago, but most entries are
one year old. So they are not updated. I update the site
frequently (perhaps I updated 200-300 entries for 2.066).
To estimate build times I'll co
On Thu, 28 Aug 2014 19:21:04 -0700
Andrei Alexandrescu via Digitalmars-d
wrote:
> Dear community, are you ready for this?
yes, yes and yes!
signature.asc
Description: PGP signature
On 29/08/14 04:21, Andrei Alexandrescu wrote:
Dear community, are you ready for this?
https://issues.dlang.org/show_bug.cgi?id=2834
https://github.com/D-Programming-Language/druntime/pull/864
Does this has the same issues as destructors for classes, i.e. not
guaranteed to run?
--
/Jacob Car
On Fri, 29 Aug 2014 05:31:00 +
deadalnix via Digitalmars-d wrote:
> If the value in unspecified, rather than the behavior undefined,
> it means that no load or store can be optimized away or
> reordered, unless the compiler can prove that is won't fault.
will it really hurt most programs? c
On Friday, 29 August 2014 at 05:31:02 UTC, deadalnix wrote:
If the value in unspecified, rather than the behavior
undefined, it means that no load or store can be optimized away
or reordered, unless the compiler can prove that is won't fault.
I'm talking about doubtful optimization to gain 0.5
On 28/08/14 21:27, "Marc Schütz" " wrote:
The other way round would be safer: A destructor automatically calls as
its first step a finalizer (let's use that term for a destructor called
by the GC) if present, but a finalizer doesn't call the destructor.
Remember that the things that are forbidde
On Friday, 29 August 2014 at 02:21:07 UTC, Andrei Alexandrescu
wrote:
Dear community, are you ready for this?
https://issues.dlang.org/show_bug.cgi?id=2834
https://github.com/D-Programming-Language/druntime/pull/864
We must do it, and the way I see it the earlier the better.
Shall we do it in
On Friday, 29 August 2014 at 02:10:55 UTC, ketmar via
Digitalmars-d wrote:
On Thu, 28 Aug 2014 09:12:15 +
deadalnix via Digitalmars-d wrote:
It forces all the load to potentially have side effects,
which, in turn, limit dramatically what the optimizer can do.
but there is alot code that do
On Fri, Aug 29, 2014 at 02:36:21AM +, Hubert via Digitalmars-d wrote:
> Thanks for the response! I do agree that the colors are way too "hot"
> (I've must've been quite tired when I submitted that mockup)
>
> Someone noted that the concept that I pitched had too much whitespace,
> which is a s
On Friday, 29 August 2014 at 04:29:31 UTC, Vladimir Panteleev
wrote:
On Friday, 29 August 2014 at 04:21:54 UTC, Andrew Godfrey wrote:
The first parameter of formattedRead is a non-const ref. Is
there
a good reason for this?
formattedRead takes an input range as the first parameter, and
consu
const(char)[] tmp = date;
enforce(3 == formattedRead(tmp, "%d/%d/%d", &month,
&day, &year));
On Friday, 29 August 2014 at 04:21:54 UTC, Andrew Godfrey wrote:
The first parameter of formattedRead is a non-const ref. Is
there
a good reason for this?
formattedRead takes an input range as the first parameter, and
consumes it as it is going through the format string. On exit,
the range w
The first parameter of formattedRead is a non-const ref. Is there
a good reason for this?
e.g. the below doesn't compile, but if I remove the 'const' from
Foo.normalize, then it succeeds:
unittest {
import std.datetime;
struct Foo {
string date;
DateTime normalize() con
On Friday, 29 August 2014 at 02:21:07 UTC, Andrei Alexandrescu
wrote:
Dear community, are you ready for this?
Yes.
On Friday, 29 August 2014 at 03:32:45 UTC, Andrei Alexandrescu
wrote:
On 8/28/14, 8:07 PM, Jonathan M Davis wrote:
Since this is in the library, not the compiler, I'm not sure
how you'd
do that (have the compiler specific a version identifier for
it?), but
considering how broken the behavior wa
On Friday, 29 August 2014 at 03:07:06 UTC, Jonathan M Davis wrote:
and that we don't normally provide flags to revert changes in
behavior
Exactly the culture I am trying to change here.
Either companion flag in compiler that prints places where
structs are going to be "destructored" now or ru
On 8/28/14, 8:07 PM, Jonathan M Davis wrote:
Since this is in the library, not the compiler, I'm not sure how you'd
do that (have the compiler specific a version identifier for it?), but
considering how broken the behavior was before and that we don't
normally provide flags to revert changes in b
On Friday, 29 August 2014 at 02:59:07 UTC, Dicebot wrote:
On Friday, 29 August 2014 at 02:21:07 UTC, Andrei Alexandrescu
wrote:
Dear community, are you ready for this?
https://issues.dlang.org/show_bug.cgi?id=2834
https://github.com/D-Programming-Language/druntime/pull/864
We must do it, and t
On Friday, 29 August 2014 at 02:36:22 UTC, Hubert wrote:
You may feel that a "Getting started" section and simplified
link/navigation structure might be insulting or inefficient,
but is the site supposed to cater to the entrenched
D-practitioners? As long as the readability and the layout of
t
On Friday, 29 August 2014 at 02:21:07 UTC, Andrei Alexandrescu
wrote:
Dear community, are you ready for this?
https://issues.dlang.org/show_bug.cgi?id=2834
https://github.com/D-Programming-Language/druntime/pull/864
We must do it, and the way I see it the earlier the better.
Shall we do it in
On 8/28/2014 7:54 PM, Brad Roberts via Digitalmars-d wrote:
I didn't study the changes, except to note that the number of tests
seems rather considering the nature of what's changing.
Er: rather LOW considering...
On Friday, 29 August 2014 at 02:10:47 UTC, Jeremy Powers via
Digitalmars-d wrote:
On Wed, Aug 27, 2014 at 12:30 PM, Nick Sabalausky via
Digitalmars-d <
digitalmars-d@puremagic.com> wrote:
Therefore, I think the main critera we should be looking at
here, for any
of the possibilities, isn't "Doe
On 8/28/2014 7:21 PM, Andrei Alexandrescu via Digitalmars-d wrote:
Dear community, are you ready for this?
https://issues.dlang.org/show_bug.cgi?id=2834
https://github.com/D-Programming-Language/druntime/pull/864
We must do it, and the way I see it the earlier the better. Shall we do
it in 2.06
On Friday, 29 August 2014 at 02:21:07 UTC, Andrei Alexandrescu
wrote:
Dear community, are you ready for this?
https://issues.dlang.org/show_bug.cgi?id=2834
https://github.com/D-Programming-Language/druntime/pull/864
We must do it, and the way I see it the earlier the better.
Shall we do it in
On Friday, 29 August 2014 at 02:21:07 UTC, Andrei Alexandrescu
wrote:
Dear community, are you ready for this?
https://issues.dlang.org/show_bug.cgi?id=2834
https://github.com/D-Programming-Language/druntime/pull/864
We must do it, and the way I see it the earlier the better.
Shall we do it in
Thanks for the response! I do agree that the colors are way too
"hot" (I've must've been quite tired when I submitted that mockup)
Someone noted that the concept that I pitched had too much
whitespace, which is a sentiment that I do not share. There's a
lot of issues with the readability in th
On Thu, Aug 28, 2014 at 07:21:04PM -0700, Andrei Alexandrescu via Digitalmars-d
wrote:
> Dear community, are you ready for this?
>
> https://issues.dlang.org/show_bug.cgi?id=2834
> https://github.com/D-Programming-Language/druntime/pull/864
>
> We must do it, and the way I see it the earlier the
On 8/28/2014 9:21 PM, Andrei Alexandrescu wrote:
Dear community, are you ready for this?
https://issues.dlang.org/show_bug.cgi?id=2834
https://github.com/D-Programming-Language/druntime/pull/864
We must do it, and the way I see it the earlier the better. Shall we do
it in 2.067?
This is a sign
Dear community, are you ready for this?
https://issues.dlang.org/show_bug.cgi?id=2834
https://github.com/D-Programming-Language/druntime/pull/864
We must do it, and the way I see it the earlier the better. Shall we do
it in 2.067?
This is a significant change of behavior. Should we provide a
On Friday, 29 August 2014 at 02:10:57 UTC, Russel Winder via
Digitalmars-d wrote:
Jérôme,
On Thu, 2014-08-28 at 11:53 +0200, "Jérôme M. Berger" via
Digitalmars-d
wrote:
[…]
PPS: IANAL but I have had lots of contacts with patent lawyers
and I
have taken part in several patent disputes as an ex
On Monday, 25 August 2014 at 16:40:10 UTC, Jonathan Marler wrote:
Hello everyone,
I've been working on SDL support for DUB and wanted to get some
people's opinions on whether we should really use SDL. I've
posted my thoughts here:
http://forum.rejectedsoftware.com/groups/rejectedsoftware.dub
On Thursday, 28 August 2014 at 05:13:06 UTC, Andrei Alexandrescu
wrote:
On 8/27/14, 9:47 PM, Andrew Edwards wrote:
Anyone here knows how to consistently obtain the previous tag
on git?
Are tags always coming in order? Then it's easy:
git tag | tail -n2 | head -n1
Andrei
Not in semver orde
On Friday, 29 August 2014 at 00:50:35 UTC, Israel wrote:
Believe it or not, many of us are here because of that very
reason, we want something that is just or nearly as good as
C/C++
but without the mess. Even if its still using the C/C++ training
wheels.
Of course, but that inevitably leads
I found https://github.com/acmeism/RosettaCodeData. Is it fresh?
To estimate build times I'll concatenate all files into one.
About 6K LOC. Then I'll duplicate that file. Sound good?
Scott
On Thursday, 28 August 2014 at 19:51:22 UTC, bearophile wrote:
Scott Wilson:
What is a large program o
On Thursday, 28 August 2014 at 18:30:09 UTC, Jonathan M Davis
wrote:
On Thursday, 28 August 2014 at 17:49:44 UTC, Vic Cekvenich The
"new" stuff int he language would basically just be cleaning up
existing features in C rather than adding anything major to it.
So, you'd get a language that's mor
These are of similar nature I believe for c++
http://www.csse.monash.edu.au/~damian/papers/PDF/ModestProposal.pdf
http://www.csse.monash.edu.au/~damian/papers/PDF/SPECS.pdf
This paper was by my c++ lecturer at the time it was published. A
fantastic coder as well as academic who unfortunately wa
On Thursday, 28 August 2014 at 19:47:13 UTC, Nick Sabalausky
wrote:
On 8/28/2014 5:29 AM, Kagamin wrote:
and the only way
to make them scale is to turn them into syntactical equivalent
of XML
with closing tags. And even then more verbose than XML itself.
So what's
a difference from XML if good
Scott Wilson:
What is a large program on rosetta?
I answered this post, but I can't see my post. If you compile a
long D C-like program you have a smaller compile time compared to
compiling a shorter D program that uses std.algorithm and
std.range a lot, because of all the templates that ne
On 8/28/2014 5:29 AM, Kagamin wrote:
On Wednesday, 27 August 2014 at 19:30:35 UTC, Nick Sabalausky wrote:
Besides, there's nothing stopping a good editor from taking this:
{
"tag1" : {
...blah, blah, blah, blah...
...blah, blah, blah, blah...
...blah, blah, blah, bla
On Thursday, 28 August 2014 at 18:53:25 UTC, Jacob Carlborg wrote:
On 2014-08-28 11:16, "Marc Schütz" " wrote:
I'd rather introduce a special method that is called only by
the GC.
Cleaning up after an object that goes out of scope has always
been the
task of the regular destructor, it's undete
On 2014-08-28 11:16, "Marc Schütz" " wrote:
I'd rather introduce a special method that is called only by the GC.
Cleaning up after an object that goes out of scope has always been the
task of the regular destructor, it's undeterministic destruction that
needs special treatment.
I was think abo
On 2014-08-28 13:49, Chris wrote:
Is there any chance this could be made available on the server?
DMD 2.065.0 is available here: ftp://ftp.digitalmars.com/dmd.2.065.0.zip
--
/Jacob Carlborg
On Thursday, 28 August 2014 at 17:49:44 UTC, Vic Cekvenich wrote:
I think interesting/relevant:
- http://blog.regehr.org/archives/1180
This reminds me of how one of my coworkers suggested at one point
that it would be great if someone created cleaner, safer C - but
didn't try and add fancy f
On 08/28/2014 07:34 PM, Walter Bright wrote:
Aliases are not really prior art either since they do not allow
creating an immutable type without also creating the corresponding
mutable type.
This seems to me to be reductio ad absurdum. And how does the patent say
an immutable T is to be cr
I think interesting/relevant:
- http://blog.regehr.org/archives/1180
Cheers,
Vic
On Thu, Aug 28, 2014 at 10:34:16AM -0700, Walter Bright via Digitalmars-d wrote:
[...]
> It's more than immutable, you're right. D also has transitive
> immunity, which is a feature of the patent, and also relaxed
> immutability during construction, which is also a point in the patent.
>
> In fact
On Wednesday, 27 August 2014 at 06:14:10 UTC, Marco Leise wrote:
I really think this is the case where you should roll your own
FileNoThrowingLogger and go with it.
*Me* or everyone who needs to log something in a dtor?
I really believe that necessity to log something in dtor is
currently an
Hey I want to benchmark speed of D and other languages. I think
I'll use rosetta code. It has functional equivalent code in
several langs.
What is a large program on rosetta? I will copy that program many
times and modify each with sed so the names are abit different.
Then write a makefile and bu
On 8/28/2014 2:53 AM, "Jérôme M. Berger" wrote:
I should have said that in D it is used when declaring an instance
(i.e. at the place of the instance declaration) whereas in the
patent it is used when declaring the type. For a patent lawyer, this
will be enough to say that the patent is n
Kahan states this in a 1997 paper:
«[…]An SNaN may be moved ( copied ) without incident, but any
other arithmetic operation upon an SNaN is an INVALID operation (
and so is loading one onto the ix87's stack ) that must trap or
else produce a new nonsignaling NaN. ( Another way to turn an
SNaN
Let me try again:
SNAN => unfortunately absent
QNAN => deliberately absent
So you can have:
compute(SNAN) => handle(exception) {
if(can turn unfortunate situation into deliberate)
then compute(QNAN)
else throw
)
On Thursday, 28 August 2014 at 14:43:30 UTC, Don wrote:
No. Once you load an SNAN, it isn't an SNAN any more! It is a
QNAN.
By which definition? It is only if you consume the SNAN with an
fp-exception-free arithmetic op that it should be turned into a
QNAN. If you compute with an op that thr
"Don" wrote in message news:fvxmsrbicgpqkkiuf...@forum.dlang.org...
If float.init exists, it cannot be an snan, since you are allowed to use
float.init.
So should we get rid of them from the language completely? Using them as
template parameters does even respect the sign of the NaN last ti
On Thursday, 28 August 2014 at 12:10:58 UTC, Ola Fosheim Grøstad
wrote:
Or to be more explicit:
If have SNAN then there is no point in trying to recompute the
expression using a different algorithm.
If have QNAN then you might want to recompute the expression
using a different algorithm (e.g
Older packages available in:
http://downloads.dlang.org/releases/
Direct link to the 2.065 zip file is:
http://downloads.dlang.org/releases/2014/dmd.2.065.0.zip
Kenji Hara
2014-08-28 20:49 GMT+09:00 Chris via Digitalmars-d <
digitalmars-d@puremagic.com>:
> Is there any chance this could be mad
On Wednesday, 27 August 2014 at 21:19:47 UTC, Walter Bright wrote:
On 8/27/2014 1:02 PM, "Jérôme M. Berger" wrote:
So for patent number 20140196015, the application number is
13/734762 and for patent number 20140196008, the application
number
is 13/734750.
Jerome
"R
On 08/28/2014 11:53 AM, "Jérôme M. Berger" wrote:
...
I should have said that in D it is used when declaring an instance
(i.e. at the place of the instance declaration) whereas in the
patent it is used when declaring the type. For a patent lawyer, this
will be enough to say that the pate
Or to be more explicit:
If have SNAN then there is no point in trying to recompute the
expression using a different algorithm.
If have QNAN then you might want to recompute the expression
using a different algorithm (e.g. complex numbers or
analytically).
?
On Thursday, 28 August 2014 at 11:09:16 UTC, Don wrote:
I think the way to think of it is, to the programmer, there is
*no such thing* as an snan value. It's an implementation detail
that should be invisible.
Semantically, a signalling nan is a qnan value with a hardware
breakpoint on it.
I d
Is there any chance this could be made available on the server?
On Wednesday, 27 August 2014 at 23:51:54 UTC, Walter Bright wrote:
On 8/26/2014 12:24 AM, Don wrote:
On Monday, 25 August 2014 at 23:29:21 UTC, Walter Bright wrote:
On 8/25/2014 4:15 PM, "Ola Fosheim Grøstad"
" wrote:
On Monday, 25 August 2014 at 21:24:11 UTC, Walter Bright
wrote:
I didn't kno
V Thu, 28 Aug 2014 11:53:35 +0200
"Jérôme M. Berger" via Digitalmars-d
napsáno:
>
> I should have said that in D it is used when declaring an
> instance (i.e. at the place of the instance declaration) whereas in
> the patent it is used when declaring the type. For a patent lawyer,
> this wi
Jérôme,
On Thu, 2014-08-28 at 11:53 +0200, "Jérôme M. Berger" via Digitalmars-d
wrote:
[…]
> PPS: IANAL but I have had lots of contacts with patent lawyers and I
> have taken part in several patent disputes as an expert witness.
> However, this was in France so most of my knowledge applies to
> Fr
Dicebot wrote:
> On Wednesday, 27 August 2014 at 20:08:45 UTC, Jérôme M. Berger
> wrote:
>> Note however that as I understand it D does not have "immutable
>> types" as claimed by patent 20140196008. The difference is that
>> according to the patent the immutable attribute is given to the
>>
On Wednesday, 27 August 2014 at 19:30:35 UTC, Nick Sabalausky
wrote:
Besides, there's nothing stopping a good editor from taking
this:
{
"tag1" : {
...blah, blah, blah, blah...
...blah, blah, blah, blah...
...blah, blah, blah, blah...
...blah, blah, blah, bla
On Thu, 28 Aug 2014 09:12:15 +
deadalnix via Digitalmars-d wrote:
p.s. code generated by DMD, for example, at least two times slower than
code generated by GDC. but most people are ok with it.
signature.asc
Description: PGP signature
On Thu, 28 Aug 2014 09:12:15 +
deadalnix via Digitalmars-d wrote:
> It forces all the load to potentially have side effects, which,
> in turn, limit dramatically what the optimizer can do.
but there is alot code that doesn't need "super-speed". it's ok to
fallback to "standard C" for the par
On Thursday, 28 August 2014 at 06:52:31 UTC, Jacob Carlborg wrote:
On 24/08/14 15:14, "Marc Schütz" " wrote:
In the "Opportunities for D" thread, Walter again mentioned
the topics
ref counting, GC, uniqueness, and borrowing, from which a
lively
discussion developed [1]. I took this thread as an
On Thursday, 28 August 2014 at 07:36:28 UTC, bearophile wrote:
Found through Reddit. A nice incomplete list that specifies a
"friendly C" that replaces many occurrences of "X has undefined
behavior" with "X results in an unspecified value":
http://blog.regehr.org/archives/1180
But I agree wit
This prohibits diagnostic of integer overflow. The runtime is no
longer allowed to throw exception in such case.
Though good as an additional dialect.
On Tuesday, 26 August 2014 at 21:29:13 UTC, Nick Sabalausky wrote:
It's FAR more than just MS. For example, Apple's just as bad.
Just look at Steve Job's undying vendetta against Google (by
way of Samsung as a proxy target).
The inter-company vendetta isn't THAT big a deal, if they can
still
Found through Reddit. A nice incomplete list that specifies a
"friendly C" that replaces many occurrences of "X has undefined
behavior" with "X results in an unspecified value":
http://blog.regehr.org/archives/1180
But I agree with one comment:
memcpy and memmove ought to remain distinct, but
74 matches
Mail list logo
