On 2011-08-16 21:12, Kiith-Sa wrote:
Jacob Carlborg wrote:
On 2011-08-16 20:13, Kiith-Sa wrote:
D:YAML is a YAML parser library for D.
It is mostly compliant with the YAML 1.1 spec, although there are some
unsupported features (e.g. recursive data structures).
Currently there is only a
Jacob Carlborg wrote:
On 2011-08-16 21:12, Kiith-Sa wrote:
Jacob Carlborg wrote:
On 2011-08-16 20:13, Kiith-Sa wrote:
D:YAML is a YAML parser library for D.
It is mostly compliant with the YAML 1.1 spec, although there are some
unsupported features (e.g. recursive data structures).
On 8/17/2011 5:01 AM, Nick Sabalausky wrote:
Kiith-Sa4...@theanswer.com wrote in message
news:j2ec0p$al6$1...@digitalmars.com...
D:YAML is a YAML parser library for D.
It is mostly compliant with the YAML 1.1 spec, although there are some
unsupported features (e.g. recursive data structures).
On 2011-08-17 13:08, Kiith-Sa wrote:
Jacob Carlborg wrote:
Does the parser/lexer take advantage of D's slices to make it faster?
In some places, yes, in some places, no. I didn't concentrate on preventing
new strings from being allocated, but a lot of string data should pass
through the code
Now that Lars Kyllingstad's new and improved std.path has passed the
vote – congratulations, Lars! –, and Jose Armando Garcia, the author of
the proposed logging module, is currently not available, the etc.curl
module by Jonas Drewsen is at the front of the review queue. I have
volunteered to
On 8/16/2011 9:37 PM, Jesse Phillips wrote:
On Tue, 16 Aug 2011 21:17:31 -0700, Mehrdad wrote:
On 8/16/2011 9:05 PM, Jonathan M Davis wrote:
Sorry that this is long, but it's very important IMHO, and I don't know
how to make it much shorter and cover what it's supposed to cover.
Okay. Your
When you have Herpes, HIV/AIDS, hpv,or any other STD, it can feel like you are
all alone in the world DatingHerpesSingles.com is a place where you didn't
have to worry about being rejected Just feel free to chat, share stories,
make friends in your local area.
On Tuesday, August 16, 2011 23:20:14 Mehrdad wrote:
On 8/16/2011 9:37 PM, Jesse Phillips wrote:
On Tue, 16 Aug 2011 21:17:31 -0700, Mehrdad wrote:
On 8/16/2011 9:05 PM, Jonathan M Davis wrote:
Sorry that this is long, but it's very important IMHO, and I don't
know
how to make it much
On 2011-08-16 22:01, Jonathan M Davis wrote:
On Tuesday, August 16, 2011 18:47:44 Jacob Carlborg wrote:
BTW, do we have style guides for abbreviations like this?
No. The style guide says camelcase, but it doesn't specify how to deal with
abbreviations. Personally, I think that it should be
On 17.08.2011 3:47, bearophile wrote:
Dmitry Olshansky:
To get a small no-crap-included beta package see download section of
https://github.com/blackwhale/FReD for .7zs.
I have not patched DMD, but it gives me some problem here:
void parseFlags(S)(S flags)
{
foreach(ch; flags)//flags
On Wednesday, August 17, 2011 09:01:02 Jacob Carlborg wrote:
On 2011-08-16 22:01, Jonathan M Davis wrote:
On Tuesday, August 16, 2011 18:47:44 Jacob Carlborg wrote:
BTW, do we have style guides for abbreviations like this?
No. The style guide says camelcase, but it doesn't specify how to
On 17/08/11 5:05 AM, Jonathan M Davis wrote:
It was previously determined that this would be a problem for ranges which are
reference types (classes in particular, but it affects structs as well, if
copying them doesn't create an independent range). So, we added the save
property.
snip
On Wednesday, August 17, 2011 09:03:52 Peter Alexander wrote:
On 17/08/11 5:05 AM, Jonathan M Davis wrote:
It was previously determined that this would be a problem for ranges
which are reference types (classes in particular, but it affects
structs as well, if copying them doesn't create an
Should the documentation for RefCounted reflect the fact that it doesn't
support actual objects (the current description implies that it does), or is
the plan for it to eventually support objects?
On 16/08/11 22.39, bearophile wrote:
jdrewsen:
etc.c.curl is already in phobos and no binary library for curl is in.
I see. I didn't know this. Then it's the good moment to improve this situation.
I disagree on this one though. But please see my reply to jonathan as to
how I see final
On 17/08/11 00.21, Jonathan M Davis wrote:
On Tuesday, August 16, 2011 12:32 Martin Nowak wrote:
On Tue, 16 Aug 2011 20:48:51 +0200, jdrewsenjdrew...@nospam.com wrote:
Den 16-08-2011 18:55, Martin Nowak skrev:
On Tue, 16 Aug 2011 15:13:40 +0200, dsimchadsim...@yahoo.com wrote:
On 8/16/2011
Jonathan M Davis jmdavisp...@gmx.com wrote in message
news:mailman.2378.1313523921.14074.digitalmar...@puremagic.com...
On Wednesday, August 17, 2011 01:23:18 Daniel Murphy wrote:
Jonathan M Davis jmdavisp...@gmx.com wrote in message
On 8/16/2011 11:41 PM, Jonathan M Davis wrote:
On Tuesday, August 16, 2011 23:20:14 Mehrdad wrote:
Right, but the problem is that none of this template business (e.g.
isInputRange!T, hasLength!T, etc.) works if the input is an Object that
implements InputRange.
For example, consider this:
Dmitry Olshansky:
Yes, that's a bug. But it's not a regression,
I think it's a DMD regression, probably introduced with the recent changes in
switch semantics. DMD 2.042 doesn't have this bug.
I assume you started to compile with -w,
I suggest Phobos devs to use -w too.
thanks for
Andrei Alexandrescu:
Let's please stop this.
OK. This sub-thread about Hash resilience against attacks is a minor detail of
my original post.
kennytm has answered my point 4, but I'd like some answers to the first three
points; regarding the error messages for not complete hash protocol, the
thanks for uncovering it again, you may as well file it.
OK, I'll add it to Bugzilla.
http://d.puremagic.com/issues/show_bug.cgi?id=6518
== Quote from Walter Bright (newshou...@digitalmars.com)'s article
On 8/15/2011 12:19 PM, Jacob Carlborg wrote:
Can't we always automatically return the last expression, even if it ends
with a
semicolon?
It interferes with auto return typing (such as void returns).
Ignoring
On Wed, 17 Aug 2011 05:43:00 -0400, Jonas Drewsen jdrew...@nospam.com
wrote:
On 17/08/11 00.21, Jonathan M Davis wrote:
On Tuesday, August 16, 2011 12:32 Martin Nowak wrote:
On Tue, 16 Aug 2011 20:48:51 +0200, jdrewsenjdrew...@nospam.com
wrote:
Den 16-08-2011 18:55, Martin Nowak skrev:
On Tue, 16 Aug 2011 20:06:19 -0400, bearophile bearophileh...@lycos.com
wrote:
Walter Bright:
It wasn't changed to simplify code, it was changed because it was
faster.
And uses much less space -- only one pointer per node vs. two.
Right.
I'd add that removing the requirement for
On Wed, 17 Aug 2011 00:15:38 -0400, Andrei Alexandrescu
seewebsiteforem...@erdani.org wrote:
On 8/16/11 9:29 PM, bearophile wrote:
Walter Bright:
I think there are search trees like the Red-Black ones that guarantee
a O(n ln n) worst case. I am wrong?
Just feed it more data.
If you
On Wed, 17 Aug 2011 02:20:14 -0400, Mehrdad wfunct...@hotmail.com wrote:
On 8/16/2011 9:37 PM, Jesse Phillips wrote:
On Tue, 16 Aug 2011 21:17:31 -0700, Mehrdad wrote:
On 8/16/2011 9:05 PM, Jonathan M Davis wrote:
Sorry that this is long, but it's very important IMHO, and I don't
know
how
On Wed, 17 Aug 2011 00:05:54 -0400, Jonathan M Davis jmdavisp...@gmx.com
wrote:
So, the question is, should a range-based function have the same
behavior for
all forward ranges regardless of whether they're value types or reference
types? Or should the caller be aware of whether a range is
On 8/17/2011 7:14 AM, Steven Schveighoffer wrote:
Casting is actually the correct solution.
if(auto irange = cast(InputRangeObject)collection)
{
// now you can use irange
if(collection.empty) // success!
{
...
}
}
The correct solution? It doesn't even compile. (See my last
Den 17-08-2011 15:51, Steven Schveighoffer skrev:
On Wed, 17 Aug 2011 05:43:00 -0400, Jonas Drewsen jdrew...@nospam.com
wrote:
On 17/08/11 00.21, Jonathan M Davis wrote:
On Tuesday, August 16, 2011 12:32 Martin Nowak wrote:
On Tue, 16 Aug 2011 20:48:51 +0200, jdrewsenjdrew...@nospam.com
On Wed, 17 Aug 2011 10:56:02 -0400, Mehrdad wfunct...@hotmail.com wrote:
On 8/17/2011 7:14 AM, Steven Schveighoffer wrote:
Casting is actually the correct solution.
if(auto irange = cast(InputRangeObject)collection)
{
// now you can use irange
if(collection.empty) // success!
{
On 08/17/2011 05:05 PM, jdrewsen wrote:
Den 17-08-2011 15:51, Steven Schveighoffer skrev:
On Wed, 17 Aug 2011 05:43:00 -0400, Jonas Drewsen jdrew...@nospam.com
wrote:
On 17/08/11 00.21, Jonathan M Davis wrote:
On Tuesday, August 16, 2011 12:32 Martin Nowak wrote:
On Tue, 16 Aug 2011
On Wed, 17 Aug 2011 11:05:56 -0400, jdrewsen jdrew...@nospam.com wrote:
Den 17-08-2011 15:51, Steven Schveighoffer skrev:
On Wed, 17 Aug 2011 05:43:00 -0400, Jonas Drewsen jdrew...@nospam.com
wrote:
On 17/08/11 00.21, Jonathan M Davis wrote:
On Tuesday, August 16, 2011 12:32 Martin Nowak
On 8/17/11 12:43 AM, Walter Bright wrote:
On 8/16/2011 9:15 PM, Andrei Alexandrescu wrote:
Let's please stop this. Many of us, including yourself, noticed the
relatively
poor performance of D's previous hashtables compared to other languages.
Switching to singly-list collision handling marked
On Wednesday, August 17, 2011 10:04:21 Steven Schveighoffer wrote:
On Wed, 17 Aug 2011 00:15:38 -0400, Andrei Alexandrescu
seewebsiteforem...@erdani.org wrote:
On 8/16/11 9:29 PM, bearophile wrote:
Walter Bright:
I think there are search trees like the Red-Black ones that
guarantee
a
On 8/17/11 9:04 AM, Steven Schveighoffer wrote:
On Wed, 17 Aug 2011 00:15:38 -0400, Andrei Alexandrescu
seewebsiteforem...@erdani.org wrote:
On 8/16/11 9:29 PM, bearophile wrote:
Walter Bright:
I think there are search trees like the Red-Black ones that
guarantee a O(n ln n) worst case. I
On Wednesday, August 17, 2011 11:30:06 Steven Schveighoffer wrote:
On Wed, 17 Aug 2011 11:05:56 -0400, jdrewsen jdrew...@nospam.com wrote:
Den 17-08-2011 15:51, Steven Schveighoffer skrev:
On Wed, 17 Aug 2011 05:43:00 -0400, Jonas Drewsen
jdrew...@nospam.com
wrote:
On 17/08/11 00.21,
On Wed, 17 Aug 2011 11:47:59 -0400, Jonathan M Davis jmdavisp...@gmx.com
wrote:
On Wednesday, August 17, 2011 10:04:21 Steven Schveighoffer wrote:
On Wed, 17 Aug 2011 00:15:38 -0400, Andrei Alexandrescu
seewebsiteforem...@erdani.org wrote:
On 8/16/11 9:29 PM, bearophile wrote:
Walter
I'm all for whatever fixes hashes and makes them properly CTFE'able,
IOW no more expression is not constant for hash declarations please!
On 08/17/2011 05:58 PM, Jonathan M Davis wrote:
On Wednesday, August 17, 2011 11:30:06 Steven Schveighoffer wrote:
On Wed, 17 Aug 2011 11:05:56 -0400, jdrewsenjdrew...@nospam.com wrote:
Den 17-08-2011 15:51, Steven Schveighoffer skrev:
On Wed, 17 Aug 2011 05:43:00 -0400, Jonas Drewsen
On 2011-08-17 09:13, Jonathan M Davis wrote:
On Wednesday, August 17, 2011 09:01:02 Jacob Carlborg wrote:
On 2011-08-16 22:01, Jonathan M Davis wrote:
On Tuesday, August 16, 2011 18:47:44 Jacob Carlborg wrote:
BTW, do we have style guides for abbreviations like this?
No. The style guide
On Wednesday, August 17, 2011 08:59 Steven Schveighoffer wrote:
On Wed, 17 Aug 2011 11:47:59 -0400, Jonathan M Davis jmdavisp...@gmx.com
wrote:
On Wednesday, August 17, 2011 10:04:21 Steven Schveighoffer wrote:
On Wed, 17 Aug 2011 00:15:38 -0400, Andrei Alexandrescu
On Wed, 17 Aug 2011 10:19:31 -0400, Steven Schveighoffer wrote:
On Wed, 17 Aug 2011 00:05:54 -0400, Jonathan M Davis
jmdavisp...@gmx.com wrote:
So, the question is, should a range-based function have the same
behavior for
all forward ranges regardless of whether they're value types or
D adds a very handy feature that allows you to check for a range of
values in a single case. Is there a particular reason that the syntax
case start: .. case end: is used instead of treating the case
statement similarly to an array slice, e.g. case start .. end:?
For example:
import
On Wednesday, August 17, 2011 10:27 Vijay Nayar wrote:
D adds a very handy feature that allows you to check for a range of
values in a single case. Is there a particular reason that the syntax
case start: .. case end: is used instead of treating the case
statement similarly to an array slice,
On Wed, 17 Aug 2011 17:27:43 +, Vijay Nayar wrote:
D adds a very handy feature that allows you to check for a range of
values in a single case. Is there a particular reason that the syntax
case start: .. case end: is used instead of treating the case
statement similarly to an array
On Aug 17, 2011, at 7:04 AM, Steven Schveighoffer wrote:
Yes, but let's not forget the one valid request out of all of this -- if
trees are no longer being used, opEquals should be used insted of opCmp.
This allows more possible key types (which don't define an ordering). I think
this
On 8/17/2011 7:00 AM, Steven Schveighoffer wrote:
On Tue, 16 Aug 2011 20:06:19 -0400, bearophile bearophileh...@lycos.com wrote:
Walter Bright:
It wasn't changed to simplify code, it was changed because it was faster.
And uses much less space -- only one pointer per node vs. two.
On Wed, 17 Aug 2011 17:40:40 +, Lars T. Kyllingstad wrote:
On Wed, 17 Aug 2011 17:27:43 +, Vijay Nayar wrote:
D adds a very handy feature that allows you to check for a range of
values in a single case. Is there a particular reason that the syntax
case start: .. case end: is used
On 08/17/2011 07:27 PM, Vijay Nayar wrote:
D adds a very handy feature that allows you to check for a range of
values in a single case. Is there a particular reason that the syntax
casestart: .. caseend: is used instead of treating the case
statement similarly to an array slice, e.g. casestart
On Wed, 17 Aug 2011 13:15:27 -0400, Lars T. Kyllingstad
public@kyllingen.nospamnet wrote:
On Wed, 17 Aug 2011 10:19:31 -0400, Steven Schveighoffer wrote:
On Wed, 17 Aug 2011 00:05:54 -0400, Jonathan M Davis
jmdavisp...@gmx.com wrote:
So, the question is, should a range-based function have
Vijay Nayar:
Thanks for the post! This kind of history is pretty fascinating and I'll
give it a good read. From what I've read so far, I'm surprised at how
heated the debate becomes :)
The current syntax is a compromise of several different needs, and it's
acceptable, despite a minor
On Wed, 17 Aug 2011 14:15:52 -0400, Steven Schveighoffer wrote:
On Wed, 17 Aug 2011 13:15:27 -0400, Lars T. Kyllingstad
public@kyllingen.nospamnet wrote:
On Wed, 17 Aug 2011 10:19:31 -0400, Steven Schveighoffer wrote:
On Wed, 17 Aug 2011 00:05:54 -0400, Jonathan M Davis
On Wed, 17 Aug 2011 14:53:53 -0400, Lars T. Kyllingstad
public@kyllingen.nospamnet wrote:
On Wed, 17 Aug 2011 14:15:52 -0400, Steven Schveighoffer wrote:
On Wed, 17 Aug 2011 13:15:27 -0400, Lars T. Kyllingstad
public@kyllingen.nospamnet wrote:
On Wed, 17 Aug 2011 10:19:31 -0400, Steven
On 2011-08-17 19:48, Jonathan M Davis wrote:
On Wednesday, August 17, 2011 10:27 Vijay Nayar wrote:
D adds a very handy feature that allows you to check for a range of
values in a single case. Is there a particular reason that the syntax
casestart: .. caseend: is used instead of treating the
Den 17-08-2011 00:17, Alix Pexton skrev:
On 16/08/2011 20:55, jdrewsen wrote:
Den 16-08-2011 16:43, Alix Pexton skrev:
On 16/08/2011 12:48, Jonas Drewsen wrote:
Hi all,
This is a review request for the curl wrapper. Please read the known
issues in the top of the source file and if possible
On 17/08/2011 20:35, Jacob Carlborg wrote:
D should have a built-in range type.
+1 or maybe +2 if I get an extra vote ;)
One that supports syntax for both
including and excluding the last element:
auto a = 3 .. 5
auto b = 3 ... 5
begin bikeshedding
Then we wouldn't need a special range
On 17.08.2011 21:35, Jacob Carlborg wrote:
On 2011-08-17 19:48, Jonathan M Davis wrote:
On Wednesday, August 17, 2011 10:27 Vijay Nayar wrote:
D adds a very handy feature that allows you to check for a range of
values in a single case. Is there a particular reason that the syntax
casestart: ..
On 08/17/2011 09:35 PM, Jacob Carlborg wrote:
On 2011-08-17 19:48, Jonathan M Davis wrote:
On Wednesday, August 17, 2011 10:27 Vijay Nayar wrote:
D adds a very handy feature that allows you to check for a range of
values in a single case. Is there a particular reason that the syntax
casestart:
On Wednesday, August 17, 2011 12:35 Jacob Carlborg wrote:
On 2011-08-17 19:48, Jonathan M Davis wrote:
On Wednesday, August 17, 2011 10:27 Vijay Nayar wrote:
D adds a very handy feature that allows you to check for a range of
values in a single case. Is there a particular reason that the
Jacob Carlborg:
D should have a built-in range type. One that supports syntax for both
including and excluding the last element:
auto a = 3 .. 5
auto b = 3 ... 5
Then we wouldn't need a special range syntax for switch statements.
Regarding just switches, GCC has a non standard syntax
On Wed, 17 Aug 2011 18:21:00 +0200, Timon Gehr timon.g...@gmx.ch wrote:
On 08/17/2011 05:58 PM, Jonathan M Davis wrote:
On Wednesday, August 17, 2011 11:30:06 Steven Schveighoffer wrote:
On Wed, 17 Aug 2011 11:05:56 -0400, jdrewsenjdrew...@nospam.com
wrote:
Den 17-08-2011 15:51, Steven
On Wed, 17 Aug 2011 16:29:19 -0400, bearophile wrote:
Jacob Carlborg:
D should have a built-in range type. One that supports syntax for both
including and excluding the last element:
auto a = 3 .. 5
auto b = 3 ... 5
Then we wouldn't need a special range syntax for switch statements.
On 8/17/2011 11:33 AM, bearophile wrote:
Andrei Alexandrescu:
Let's please stop this.
OK, but I'd like to note that what I have written comes from some experiments
too:
http://is.gd/L4U3Kp
I don't think it's a sensible point of view. If you supply your own hash
function, the onus is on
On Wednesday, August 17, 2011 13:31 Martin Nowak wrote:
Not wanting to drift too far off topic I'll add one last point.
given:
immutable(int[]) data = assumeUnique(myints);
send(cast(int[])data);
writeln(data[0]);
A compiler implementation could deduce data won't change between
Walter:
Bottom line, I don't think there's an actual problem here.
Thank you for your answers. And I agree that the current situation is overall
better than the precedent one.
My original first post of this thread was about other problems, quite more
practical ones, like receiving help from
On Aug 17, 2011, at 2:36 PM, bearophile wrote:
Walter:
Bottom line, I don't think there's an actual problem here.
Thank you for your answers. And I agree that the current situation is overall
better than the precedent one.
My original first post of this thread was about other
On 08/17/2011 11:09 PM, Jonathan M Davis wrote:
On Wednesday, August 17, 2011 13:31 Martin Nowak wrote:
Not wanting to drift too far off topic I'll add one last point.
given:
immutable(int[]) data = assumeUnique(myints);
send(cast(int[])data);
writeln(data[0]);
A compiler implementation could
On 8/17/11 2:35 PM, Jacob Carlborg wrote:
On 2011-08-17 19:48, Jonathan M Davis wrote:
On Wednesday, August 17, 2011 10:27 Vijay Nayar wrote:
D adds a very handy feature that allows you to check for a range of
values in a single case. Is there a particular reason that the syntax
casestart: ..
Now that Lars Kyllingstad's new and improved std.path has passed the
vote – congratulations, Lars! –, and Jose Armando Garcia, the author of
the proposed logging module, is currently not available, the etc.curl
module by Jonas Drewsen is at the front of the review queue. I have
volunteered to
On Wednesday, August 17, 2011 15:48 Timon Gehr wrote:
On 08/17/2011 11:09 PM, Jonathan M Davis wrote:
On Wednesday, August 17, 2011 13:31 Martin Nowak wrote:
Not wanting to drift too far off topic I'll add one last point.
given:
immutable(int[]) data = assumeUnique(myints);
On Thu, Aug 18, 2011 at 8:40 AM, Sean Kelly s...@invisibleduck.org wrote:
On Aug 17, 2011, at 2:36 PM, bearophile wrote:
Walter:
Bottom line, I don't think there's an actual problem here.
Thank you for your answers. And I agree that the current situation is
overall better than the
On Wed, 17 Aug 2011 10:46:00 -0500, Andrei Alexandrescu wrote:
On 8/17/11 9:04 AM, Steven Schveighoffer wrote:
On Wed, 17 Aug 2011 00:15:38 -0400, Andrei Alexandrescu
seewebsiteforem...@erdani.org wrote:
On 8/16/11 9:29 PM, bearophile wrote:
Walter Bright:
I think there are search trees
On Thu, 18 Aug 2011 01:12:20 +0200, David Nadlinger wrote:
Now that Lars Kyllingstad's new and improved std.path has passed the
vote – congratulations, Lars! –, and Jose Armando Garcia, the author of
the proposed logging module, is currently not available, the etc.curl
module by Jonas
On Wed, 17 Aug 2011 15:40:25 -0700, Sean Kelly wrote:
This would be a run-time issue, unless you're asking the compiler to
verify your hash algorithm at compile-time :-p I'd actually like to
have some introspection functionality so I could find out the average
chain length, max chain length,
On Wed, 17 Aug 2011 22:36:14 -0400, Mehrdad wfunct...@hotmail.com wrote:
On 8/17/2011 8:26 AM, Steven Schveighoffer wrote:
On Wed, 17 Aug 2011 10:56:02 -0400, Mehrdad wfunct...@hotmail.com
wrote:
On 8/17/2011 7:14 AM, Steven Schveighoffer wrote:
Casting is actually the correct solution.
On 8/17/2011 8:26 AM, Steven Schveighoffer wrote:
On Wed, 17 Aug 2011 10:56:02 -0400, Mehrdad wfunct...@hotmail.com
wrote:
On 8/17/2011 7:14 AM, Steven Schveighoffer wrote:
Casting is actually the correct solution.
if(auto irange = cast(InputRangeObject)collection)
{
// now you can use
On Wed, 17 Aug 2011 21:07:29 -0400, Jesse Phillips
jessekphillip...@gmail.com wrote:
On Wed, 17 Aug 2011 10:46:00 -0500, Andrei Alexandrescu wrote:
On 8/17/11 9:04 AM, Steven Schveighoffer wrote:
On Wed, 17 Aug 2011 00:15:38 -0400, Andrei Alexandrescu
seewebsiteforem...@erdani.org wrote:
On Wed, 17 Aug 2011 21:07:29 -0400, Jesse Phillips
jessekphillip...@gmail.com wrote:
On Wed, 17 Aug 2011 10:46:00 -0500, Andrei Alexandrescu wrote:
On 8/17/11 9:04 AM, Steven Schveighoffer wrote:
On Wed, 17 Aug 2011 00:15:38 -0400, Andrei Alexandrescu
seewebsiteforem...@erdani.org wrote:
On 8/16/2011 7:48 AM, Jonas Drewsen wrote:
Hi all,
This is a review request for the curl wrapper. Please read the known
issues in the top of the source file and if possible suggest a solution.
We also need somebody for running the review process. Anyone?
Code:
On Wed, Aug 17, 2011 at 10:41 PM, dsimcha dsim...@yahoo.com wrote:
On 8/16/2011 7:48 AM, Jonas Drewsen wrote:
Hi all,
This is a review request for the curl wrapper. Please read the known
issues in the top of the source file and if possible suggest a solution.
We also need somebody for
code
abstract class Parent {
abstract void method();
}
class Child : Parent {}
void main(string[] args) {
new Child;
}
/code
output
src/test.d(10): Error: cannot create instance of abstract class Child
src/test.d(10): Error: function method is abstract
/output
Is this really
On Thursday, August 18, 2011 08:39:04 Mariusz Gliwiński wrote:
code
abstract class Parent {
abstract void method();
}
class Child : Parent {}
void main(string[] args) {
new Child;
}
/code
output
src/test.d(10): Error: cannot create instance of abstract class Child
Dnia środa, 17 sierpnia 2011 22:23:04 Jonathan M Davis pisze:
I'm afraid that I don't quite get what you're trying to say.
Oh no, again :( I wonder if it's language bareer or just my freaky mind
bareer.
Now, I would argue that it should probably be required that Child either
override all of
On 2011-08-17 03:36, Jesse Phillips wrote:
On Tue, 16 Aug 2011 18:46:28 +0200, Jacob Carlborg wrote:
Not all top level directories need to be submodules, that was just a
thought. I could include everything to make it possible to build DWT in
one repository (the super repository) and have
On 16.08.2011 18:46, Jacob Carlborg wrote:
On 2011-08-16 16:30, Jesse Phillips wrote:
It is almost like that. It's just that the cloning also requires the
initialization and cloning of the submodules. You'll have to keep them in
sync and I've never submoduled a project that had submodules it
On Wed, 17 Aug 2011 11:46:23 +0200, torhu wrote:
If submodules are meant for the same use cases as SVN externals, they
are primarily for automatically pulling in stuff that is separate
because it is actually a separate project, probably maintained by
someone else, or maybe just hosted
On 2011-08-17 11:46, torhu wrote:
On 16.08.2011 18:46, Jacob Carlborg wrote:
On 2011-08-16 16:30, Jesse Phillips wrote:
It is almost like that. It's just that the cloning also requires the
initialization and cloning of the submodules. You'll have to keep
them in
sync and I've never submoduled
torhu Wrote:
Okay, I think I get the picture now. Sounds like a good plan, then.
Would DWT become a single repository with all platform implementations
and snippets in it, that has the base Java library as a submodule? Or
would it be dwt-win, dwt-linux, dwt-snippets, etc.? The former
On 2011-08-17 18:58, torhu wrote:
Okay, I think I get the picture now. Sounds like a good plan, then.
Would DWT become a single repository with all platform implementations
and snippets in it, that has the base Java library as a submodule? Or
would it be dwt-win, dwt-linux, dwt-snippets, etc.?
On 2011-08-17 20:18, Jesse Phillips wrote:
torhu Wrote:
Okay, I think I get the picture now. Sounds like a good plan, then.
Would DWT become a single repository with all platform implementations
and snippets in it, that has the base Java library as a submodule? Or
would it be dwt-win,
On Wed, 17 Aug 2011 21:26:14 +0200, Jacob Carlborg wrote:
Java runtime
Eclipse runtime (java runtime)
DWT (Eclipse runtime)
JFace (DWT)
snippets (jface)
This is how the dependencies look like. Read - as depends on
Java runtime -
Eclipse runtime - java runtime
DWT - Eclipse runtime,
Jouko Koski:
While 1_000_000 may be the right thing in program code, the outside world
would probably like to have numbers printed out according to their locale
conventions. This is even more important with floating point or monetary
values.
So before just adding some formatter to
Andrej Mitrovic andrej.mitrov...@gmail.com kirjoitti:
Okay but I wasn't really thinking about locales, underscores between
digits is a D syntax feature and it makes numbers more readable.
I agree that using almost any (thousand) separator can make reading long
numeric strings easier. I would
Am 15.08.2011, 18:06 Uhr, schrieb Andrej Mitrovic
andrej.mitrov...@gmail.com:
On 8/15/11, Steven Schveighoffer schvei...@yahoo.com wrote:
Ouch!
It's not that big of an ouch actually: http://codepad.org/m1zKlP0e
Compiled in optimized 64-bit with dmd it gives me:
old: 393 ms
new: 310 ms
http://d.puremagic.com/issues/show_bug.cgi?id=6516
Summary: [2.055 beta] ICE: assert constfold.c(721)
global.errors
Product: D
Version: D2
Platform: Other
OS/Version: Windows
Status: NEW
Keywords:
http://d.puremagic.com/issues/show_bug.cgi?id=6516
--- Comment #1 from Nick Sabalausky cbkbbej...@mailinator.com 2011-08-16
23:41:16 PDT ---
I think this may be another manifestation of the same bug:
dstring foo()
{
auto result = new dchar[](1);
result[0..1] = ad;
return
http://d.puremagic.com/issues/show_bug.cgi?id=6510
--- Comment #2 from Dmitry Olshansky dmitry.o...@gmail.com 2011-08-17
02:52:42 PDT ---
Created an attachment (id=1018)
test case, stripped down parser
--
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
--- You
http://d.puremagic.com/issues/show_bug.cgi?id=6510
--- Comment #3 from Dmitry Olshansky dmitry.o...@gmail.com 2011-08-17
02:55:11 PDT ---
I've managed to get a resonably sized test case.
Apparently it has soemthing to do with -inline:
dmd fred.d // Ok
dmd -inline fred.d //same error as
http://d.puremagic.com/issues/show_bug.cgi?id=6517
Summary: [CTFE] ptr++ doesn't work but ++ptr does
Product: D
Version: unspecified
Platform: Other
OS/Version: Windows
Status: NEW
Keywords: rejects-valid
Severity:
http://d.puremagic.com/issues/show_bug.cgi?id=6514
David Simcha dsim...@yahoo.com changed:
What|Removed |Added
CC||dsim...@yahoo.com
---
1 - 100 of 116 matches
Mail list logo
