On Mon, 19 Oct 2009 00:53:48 -0400, dolive doliv...@sina.com wrote:
Robert Jacques дµ½:
On Sun, 18 Oct 2009 23:51:37 -0400, Sam Hu samhudotsa...@gmail.com
wrote:
Robert Jacques Wrote:
Do you have a DFL for dmd2.035 ?
thank you very much !
dolive
Yes, I've e-mailed it to you.
Walter Bright wrote:
The purpose of T[new] was to solve the problems T[] had with passing T[]
to a function and then the function resizes the T[]. What happens with
the original?
The solution we came up with was to create a third array type, T[new],
which was a reference type.
Andrei had
Robert Jacques Wrote:
DMD 2.035 didn't require any patches from DMD 2.034 for DFL. I've created
a list with both you and dolive for future reference.
Many... thanks!!
Could somebody explain memory rules in class inheriting?
The following code illustrates my problem, look at 'main' function:
//
module window;
private import base;
private import structs;
private static import user32;
private static import kernel32;
Robert Jacques дµ½:
On Mon, 19 Oct 2009 00:53:48 -0400, dolive doliv...@sina.com wrote:
Robert Jacques ôµ½:
On Sun, 18 Oct 2009 23:51:37 -0400, Sam Hu samhudotsa...@gmail.com
wrote:
Robert Jacques Wrote:
Do you have a DFL for dmd2.035 ?
thank you very much !
dolive wrote:
Denis Koroskin дµ½:
On Sat, 17 Oct 2009 22:55:44 +0400, dolive doliv...@sina.com wrote:
Eldar Insafutdinov �´µ½:
dolive Wrote:
bug fix is slower,should speed up the progress, fix more than 200 a
month.
Very much looking forward to, thanks all !
dolive
What have
Moritz Warning:
foreach(key; aa.keys)
if(Test(key))
aa.remove(key);
It's undefined behavior.
You shouldn't try to mutate the aa while iterating.
I hope that will be fixed.
It took me some time to find this out.
In Python:
d = {1:2, 3:4}
for k in d: del d[k]
...
Traceback
On 2009-10-17 22:11:56 +0200, Nick Sabalausky a...@a.a said:
Only on 64-bit systems. Which are already ridiculously fast anyway. So what
if they get some more performance? They already have gobs of performance to
spare. On a 32-bit system it changes the programs performance down to It
don't f**
Don дµ½:
dolive wrote:
Denis Koroskin дµ½:
On Sat, 17 Oct 2009 22:55:44 +0400, dolive doliv...@sina.com wrote:
Eldar Insafutdinov ôµ½:
dolive Wrote:
bug fix is slower,should speed up the progress, fix more than 200 a
month.
Very much looking forward to, thanks all
Walter Bright Wrote:
The purpose of T[new] was to solve the problems T[] had with passing T[]
to a function and then the function resizes the T[]. What happens with
the original?
Why do you need such feature built into language? So many proposals to
implement this feature and that feature
dolive wrote:
Don дµ½:
dolive wrote:
Denis Koroskin дµ½:
On Sat, 17 Oct 2009 22:55:44 +0400, dolive doliv...@sina.com wrote:
Eldar Insafutdinov �´µ½:
dolive Wrote:
bug fix is slower,should speed up the progress, fix more than 200 a
month.
Very much looking forward to, thanks
Andrei Alexandrescu Wrote:
Paradoxically this seems to be conducive to subtle efficiency issues.
For example, consider:
int[new] a;
...
a = [1, 2, 3];
What should that do?
a = new Appender!int([1,2,3]);
What you describe is more like StringBuilder, and, yes, things like that
require
Can you author please be able to upgrade it to latest version of d2 ?
thank you very much !
dolive
Don дµ½:
dolive wrote:
Don дµ½:
dolive wrote:
Denis Koroskin дµ½:
On Sat, 17 Oct 2009 22:55:44 +0400, dolive doliv...@sina.com wrote:
Eldar Insafutdinov ôµ½:
dolive Wrote:
bug fix is slower,should speed up the progress, fix more than 200 a
month.
Very much
BCS n...@anon.com wrote in message
news:a6268ffb8018cc1e47bb9fc...@news.digitalmars.com...
Hello Nick,
BCS n...@anon.com wrote in message
If mine did that I'd shoot him (a scorching e-mail :)
You should both feel lucky. The best I had was a class where we filled
in the bodies of a handful
Walter Bright Wrote:
The purpose of T[new] was to solve the problems T[] had with passing T[]
to a function and then the function resizes the T[]. What happens with
the original?
The solution we came up with was to create a third array type, T[new],
which was a reference type.
Andrei
Ary Borenszweig wrote:
I remember seeing a lot of CTFE code that created a dynamic array and
then appended stuff to it, like for example to build a list of prime
numbers. Would that still work with ArrayBuilder?
Probably not. But you can rewrite:
a ~= stuff;
as:
a = a ~ stuff;
to make
Try compiling with -gc and run it under the debugger.
Ellery Newcomer wrote:
ANTLR has pretty good support for backtracking, so writing a D grammar
for it wasn't too difficult, but then the resultant performance isn't
anything near what I'd like.
My recommendation is to forget about parser generators and just build
one by hand. They're easy to
BCS wrote:
(BTW I'm taking (but haven't yet finished) a compilers class so I might
be missing something)
That's one of my gripes about compiler classes, they expend enormous
effort on the simplest part of a compiler - the lexer/parser.
In working on the D compiler, I easily spend less than
Nick Sabalausky wrote:
(Cue Walter reminiscing about how great Caltech was... ;) )
The only software course I took at Caltech was a Fortran one. I can't
remember anything about it g.
Walter Bright Wrote:
Ellery Newcomer wrote:
ANTLR has pretty good support for backtracking, so writing a D grammar
for it wasn't too difficult, but then the resultant performance isn't
anything near what I'd like.
My recommendation is to forget about parser generators and just build
On 2009-10-18 20:01:26 +0200, language_fan f...@bar.com.invalid said:
Sun, 18 Oct 2009 16:35:53 +0200, Fawzi Mohamed thusly wrote:
On 2009-10-18 11:32:07 +0200, language_fan f...@bar.com.invalid said:
Sat, 17 Oct 2009 22:56:44 -0400, Just Visiting thusly wrote:
I won't deny that for
On Mon, Oct 19, 2009 at 2:48 AM, Walter Bright
newshou...@digitalmars.com wrote:
Ary Borenszweig wrote:
I remember seeing a lot of CTFE code that created a dynamic array and then
appended stuff to it, like for example to build a list of prime numbers.
Would that still work with ArrayBuilder?
On Mon, 19 Oct 2009 05:16:45 +0400, Andrei Alexandrescu
seewebsiteforem...@erdani.org wrote:
dsimcha wrote:
== Quote from Andrei Alexandrescu (seewebsiteforem...@erdani.org)'s
article
3. A T[new] should be implicitly convertible to a slice. For
example:
auto foo =
Zarathustra wrote:
Could somebody explain memory rules in class inheriting?
The following code illustrates my problem, look at 'main' function:
Posts like this belong on d.learn.
//
module window;
private import base;
private import structs;
Mon, 19 Oct 2009 13:22:34 +0200, Fawzi Mohamed thusly wrote:
On 2009-10-18 20:01:26 +0200, language_fan f...@bar.com.invalid said:
Sun, 18 Oct 2009 16:35:53 +0200, Fawzi Mohamed thusly wrote:
Also note that cache size is heavily constrained and larger
binaries will fill it with less code.
Sun, 18 Oct 2009 18:01:51 -0400, bearophile thusly wrote:
Denis Koroskin:
Why would you want to port C code to D, if you can easily interface with
it?
First of all you have to consider programmer experience, they know C, so
keeping the language backwards compatible with C helps them avoid
This discussion originated in the T[new] thread, but I think it deserves its own
thread.
== Quote from Denis Koroskin (2kor...@gmail.com)'s article
An Array!(T) is really just a different name to a T[new]. You'll have the
same problem explaining difference between Array!(T) and T[].
But you
dsimcha wrote:
This discussion originated in the T[new] thread, but I think it deserves its own
thread.
== Quote from Denis Koroskin (2kor...@gmail.com)'s article
An Array!(T) is really just a different name to a T[new]. You'll have the
same problem explaining difference between Array!(T) and
Denis Koroskin wrote:
On Mon, 19 Oct 2009 17:13:46 +0400, dsimcha dsim...@yahoo.com wrote:
This discussion originated in the T[new] thread, but I think it
deserves its own
thread.
== Quote from Denis Koroskin (2kor...@gmail.com)'s article
An Array!(T) is really just a different name to a
On Mon, 19 Oct 2009 17:13:46 +0400, dsimcha dsim...@yahoo.com wrote:
This discussion originated in the T[new] thread, but I think it deserves
its own
thread.
== Quote from Denis Koroskin (2kor...@gmail.com)'s article
An Array!(T) is really just a different name to a T[new]. You'll have
the
== Quote from Don (nos...@nospam.com)'s article
Denis Koroskin wrote:
On Mon, 19 Oct 2009 17:13:46 +0400, dsimcha dsim...@yahoo.com wrote:
This discussion originated in the T[new] thread, but I think it
deserves its own
thread.
== Quote from Denis Koroskin (2kor...@gmail.com)'s
== Quote from downs (default_357-l...@yahoo.de)'s article
Walter Bright wrote:
Ary Borenszweig wrote:
I remember seeing a lot of CTFE code that created a dynamic array and
then appended stuff to it, like for example to build a list of prime
numbers. Would that still work with
Walter Bright wrote:
Ary Borenszweig wrote:
I remember seeing a lot of CTFE code that created a dynamic array and
then appended stuff to it, like for example to build a list of prime
numbers. Would that still work with ArrayBuilder?
Probably not. But you can rewrite:
a ~= stuff;
as:
Walter Bright wrote:
BCS wrote:
(BTW I'm taking (but haven't yet finished) a compilers class so I
might be missing something)
That's one of my gripes about compiler classes, they expend enormous
effort on the simplest part of a compiler - the lexer/parser.
In working on the D compiler, I
dsimcha wrote:
== Quote from Don (nos...@nospam.com)'s article
Denis Koroskin wrote:
On Mon, 19 Oct 2009 17:13:46 +0400, dsimcha dsim...@yahoo.com wrote:
This discussion originated in the T[new] thread, but I think it
deserves its own
thread.
== Quote from Denis Koroskin
Walter Bright írta:
The purpose of T[new] was to solve the problems T[] had with passing T[]
to a function and then the function resizes the T[]. What happens with
the original?
I've tried to follow the T[], T[new], T+slice discussion, but i'm lost,
I don't think if it's a good idea, to
Andrei Alexandrescu, el 18 de octubre a las 20:16 me escribiste:
Here's what I wrote to Walter:
I'm going to suggest something terrible - let's get rid of T[new]. I
know it's difficult to throw away work you've already done, but
really things with T[new] start to look
On Mon, 19 Oct 2009 18:57:45 +0400, Leandro Lucarella llu...@gmail.com
wrote:
Andrei Alexandrescu, el 18 de octubre a las 20:16 me escribiste:
Here's what I wrote to Walter:
I'm going to suggest something terrible - let's get rid of T[new]. I
know it's difficult to
Leandro Lucarella, el 19 de octubre a las 11:57 me escribiste:
slice.dup should return an array.
To avoid making the language aware of the array type, slice.dup can be
removed and use an array constructor instead:
auto a = slice.dup;
should be:
auto a = array!T(slice);
This way, I think the
Leandro Lucarella wrote:
Andrei Alexandrescu, el 18 de octubre a las 20:16 me escribiste:
Here's what I wrote to Walter:
I'm going to suggest something terrible - let's get rid of T[new]. I
know it's difficult to throw away work you've already done, but
really things with
Andrei Alexandrescu, el 19 de octubre a las 08:38 me escribiste:
For relatively large chunks of memory, the GC keeps a control block.
We could add a member size_t requestedSize that keeps the size that
was requested with an allocation/reallocation call. The GC can take
initiative in
Leandro Lucarella, el 19 de octubre a las 12:13 me escribiste:
Leandro Lucarella, el 19 de octubre a las 11:57 me escribiste:
slice.dup should return an array.
To avoid making the language aware of the array type, slice.dup can be
removed and use an array constructor instead:
auto a =
Leandro Lucarella wrote:
Andrei Alexandrescu, el 19 de octubre a las 08:38 me escribiste:
For relatively large chunks of memory, the GC keeps a control block.
We could add a member size_t requestedSize that keeps the size that
was requested with an allocation/reallocation call. The GC can take
== Quote from Andrei Alexandrescu (seewebsiteforem...@erdani.org)'s article
Leandro Lucarella wrote:
Andrei Alexandrescu, el 19 de octubre a las 08:38 me escribiste:
For relatively large chunks of memory, the GC keeps a control block.
We could add a member size_t requestedSize that keeps
Andrei Alexandrescu, el 19 de octubre a las 10:18 me escribiste:
Leandro Lucarella wrote:
Andrei Alexandrescu, el 18 de octubre a las 20:16 me escribiste:
Here's what I wrote to Walter:
I'm going to suggest something terrible - let's get rid of T[new]. I
know it's
On 2009-10-19 15:04:23 +0200, language_fan f...@bar.com.invalid said:
Mon, 19 Oct 2009 13:22:34 +0200, Fawzi Mohamed thusly wrote:
On 2009-10-18 20:01:26 +0200, language_fan f...@bar.com.invalid said:
Sun, 18 Oct 2009 16:35:53 +0200, Fawzi Mohamed thusly wrote:
Also note that cache size is
Andrei Alexandrescu, el 19 de octubre a las 10:33 me escribiste:
Leandro Lucarella wrote:
Andrei Alexandrescu, el 19 de octubre a las 08:38 me escribiste:
For relatively large chunks of memory, the GC keeps a control block.
We could add a member size_t requestedSize that keeps the size that
dsimcha wrote:
== Quote from Andrei Alexandrescu (seewebsiteforem...@erdani.org)'s article
Leandro Lucarella wrote:
Andrei Alexandrescu, el 19 de octubre a las 08:38 me escribiste:
For relatively large chunks of memory, the GC keeps a control block.
We could add a member size_t requestedSize
Leandro Lucarella wrote:
Andrei Alexandrescu, el 19 de octubre a las 10:18 me escribiste:
2 types should be provided: array and slice.
array is a *real* type, storing and owning memory, it should be something
like this (conceptually):
class array(T)
{
size_t length;
size_t
Andrei Alexandrescu wrote:
Leandro Lucarella wrote:
Andrei Alexandrescu, el 19 de octubre a las 10:18 me escribiste:
2 types should be provided: array and slice.
array is a *real* type, storing and owning memory, it should be
something like this (conceptually):
class array(T)
{
size_t
Hello Yigal,
I think that Arrays and AAs need to be removed from the language. I
prefer to have a collections framework as part of Phobos without
special cases in the language for specific containers.
If it can be assured that all the current array ops will get inlined is all
cases and can
Since there has been a lot of discussion here lately about how AAs and
ArrayBuilders should be implemented, we should set up a website where people
can contribute different candidate implementations and comment on them. It's
much easier to know whether something is a good idea when you have a
Andrei Alexandrescu, el 19 de octubre a las 11:16 me escribiste:
I'm missing something? Why this shouldn't work?
It may work, but I was unable to pull it off reasonably well.
What problems did you find?
I thought I explained that above and in several other posts. I have
the feeling this
Denis Koroskin wrote:
On Mon, 19 Oct 2009 20:16:50 +0400, Andrei Alexandrescu
seewebsiteforem...@erdani.org wrote:
I thought I explained that above and in several other posts. I have
the feeling this is going in circles, but let me add one more thing.
People would want to have a reasonable
On Mon, 19 Oct 2009 20:16:50 +0400, Andrei Alexandrescu
seewebsiteforem...@erdani.org wrote:
I thought I explained that above and in several other posts. I have the
feeling this is going in circles, but let me add one more thing. People
would want to have a reasonable way of choosing
Hello Walter,
BCS wrote:
(BTW I'm taking (but haven't yet finished) a compilers class so I
might be missing something)
That's one of my gripes about compiler classes, they expend enormous
effort on the simplest part of a compiler - the lexer/parser.
In working on the D compiler, I easily
Johan Granberg wrote:
I think you are seeing a larger problem than their is. But consider this,
who is D a language for, is it for beginers only? advanced users only? or
everyone, if it is a language for everyone don't complicate the language
for the advanced users by rejecting nice syntax just
dsimcha wrote:
Since there has been a lot of discussion here lately about how AAs and
ArrayBuilders should be implemented, we should set up a website where people
can contribute different candidate implementations and comment on them. It's
much easier to know whether something is a good idea
Leandro Lucarella wrote:
Andrei Alexandrescu, el 19 de octubre a las 11:16 me escribiste:
I'm missing something? Why this shouldn't work?
It may work, but I was unable to pull it off reasonably well.
What problems did you find?
I thought I explained that above and in several other posts. I
== Quote from Andrei Alexandrescu (seewebsiteforem...@erdani.org)'s article
dsimcha wrote:
Since there has been a lot of discussion here lately about how AAs and
ArrayBuilders should be implemented, we should set up a website where people
can contribute different candidate implementations
I just wrote this to Sean and Walter and subsequently discussed it with
Walter. Walter thinks this should work. Does anyone have the time and
inclination to test this out? It would involve hacking into druntime's
implementation of ~= (I'm not sure what the function name is). I'd
really
Denis Koroskin wrote:
On Mon, 19 Oct 2009 18:57:45 +0400, Leandro Lucarella llu...@gmail.com
wrote:
Andrei Alexandrescu, el 18 de octubre a las 20:16 me escribiste:
Here's what I wrote to Walter:
I'm going to suggest something terrible - let's get rid of T[new]. I
know
== Quote from Andrei Alexandrescu (seewebsiteforem...@erdani.org)'s article
I just wrote this to Sean and Walter and subsequently discussed it with
Walter. Walter thinks this should work. Does anyone have the time and
inclination to test this out? It would involve hacking into druntime's
dsimcha Wrote:
If anyone can think of any more, please let me know. Also, just thought of
this
now: I wonder if it would make sense to use some polymorphism tricks (AA
operations are slow enough that an extra pointer dereference or virtual
function
call isn't going to make or break
Andrei Alexandrescu, el 19 de octubre a las 12:40 me escribiste:
Leandro Lucarella wrote:
Andrei Alexandrescu, el 19 de octubre a las 11:16 me escribiste:
I'm missing something? Why this shouldn't work?
It may work, but I was unable to pull it off reasonably well.
What problems did you find?
== Quote from Jerry Quinn (jlqu...@optonline.net)'s article
dsimcha Wrote:
If anyone can think of any more, please let me know. Also, just thought of
this
now: I wonder if it would make sense to use some polymorphism tricks (AA
operations are slow enough that an extra pointer
dsimcha wrote:
== Quote from Andrei Alexandrescu (seewebsiteforem...@erdani.org)'s article
I just wrote this to Sean and Walter and subsequently discussed it with
Walter. Walter thinks this should work. Does anyone have the time and
inclination to test this out? It would involve hacking into
Walter Bright wrote:
The purpose of T[new] was to solve the problems T[] had with passing T[]
to a function and then the function resizes the T[]. What happens with
the original?
The solution we came up with was to create a third array type, T[new],
which was a reference type.
Andrei had
Leandro Lucarella wrote:
I don't see much problem. You should always return an array (T[new]) if
you have one, because you can get an slice from it (the inverse is not
true). Because of this, implicit conversion from array to slice can be
a good idea, so people expecting a slice when an array is
Andrei Alexandrescu, el 19 de octubre a las 13:51 me escribiste:
I just wrote this to Sean and Walter and subsequently discussed it
with Walter. Walter thinks this should work. Does anyone have the
time and inclination to test this out? It would involve hacking into
druntime's implementation
Leandro Lucarella wrote:
Andrei Alexandrescu, el 19 de octubre a las 13:51 me escribiste:
I just wrote this to Sean and Walter and subsequently discussed it
with Walter. Walter thinks this should work. Does anyone have the
time and inclination to test this out? It would involve hacking into
dsimcha wrote:
== Quote from Andrei Alexandrescu (seewebsiteforem...@erdani.org)'s
article
I just wrote this to Sean and Walter and subsequently discussed it
with Walter. Walter thinks this should work. Does anyone have the
time and inclination to test this out? It would involve hacking
into
Andrei Alexandrescu wrote:
Leandro Lucarella wrote:
Andrei Alexandrescu, el 19 de octubre a las 11:16 me escribiste:
I'm missing something? Why this shouldn't work?
It may work, but I was unable to pull it off reasonably well.
What problems did you find?
I thought I explained that above and
dsimcha wrote:
2. I don't understand how this solves the safety problem:
// foo lives on the heap b/c we've idup'd it.
string foo = This is only a test..idup;
string bar = foo[0..4];
bar ~= is _not ;
writeln(foo); // prints This is _not a test.
Having access to the capacity in an LRU cache
Don wrote:
Walter Bright wrote:
The purpose of T[new] was to solve the problems T[] had with passing
T[] to a function and then the function resizes the T[]. What happens
with the original?
The solution we came up with was to create a third array type, T[new],
which was a reference type.
Chris Nicholson-Sauls wrote:
People expecting a slice and using auto or templates are in for a
rude awakening.
Andrei
I would argue that, if they truly *needed* a slice and are relying on
auto then they implicitly accept responsibility for putting the [] in
place to guarantee that. In
Andrei Alexandrescu, el 19 de octubre a las 14:31 me escribiste:
By the way: implementation of @property has been canceled.
Keep throwing the good news :(
--
Leandro Lucarella (AKA luca) http://llucax.com.ar/
On 19/10/2009 16:57, Leandro Lucarella wrote:
Andrei Alexandrescu, el 18 de octubre a las 20:16 me escribiste:
Here's what I wrote to Walter:
I'm going to suggest something terrible - let's get rid of T[new]. I
know it's difficult to throw away work you've already done,
Bill Baxter pisze:
Just get rid of the the one-argument foreach over AAs altogether and force
the user to be
explicit about it.
I wouldn't do so. Would anybody do an error by thinking that foreach
(elem,table) should iterate over keys?
Bearophile. And anyone coming from python, at the least.
== Quote from Andrei Alexandrescu (seewebsiteforem...@erdani.org)'s article
dsimcha wrote:
2. I don't understand how this solves the safety problem:
// foo lives on the heap b/c we've idup'd it.
string foo = This is only a test..idup;
string bar = foo[0..4];
bar ~= is _not ;
On 2009-10-19 18:19:34 +0200, Andrei Alexandrescu
seewebsiteforem...@erdani.org said:
dsimcha wrote:
== Quote from Andrei Alexandrescu (seewebsiteforem...@erdani.org)'s article
Leandro Lucarella wrote:
Andrei Alexandrescu, el 19 de octubre a las 08:38 me escribiste:
For relatively large
dsimcha wrote:
== Quote from Andrei Alexandrescu (seewebsiteforem...@erdani.org)'s article
dsimcha wrote:
2. I don't understand how this solves the safety problem:
// foo lives on the heap b/c we've idup'd it.
string foo = This is only a test..idup;
string bar = foo[0..4];
bar ~= is _not ;
On Mon, 19 Oct 2009 23:31:37 +0400, Andrei Alexandrescu
seewebsiteforem...@erdani.org wrote:
Don wrote:
Walter Bright wrote:
The purpose of T[new] was to solve the problems T[] had with passing
T[] to a function and then the function resizes the T[]. What happens
with the original?
The
Don pisze:
Since noone else seems to have said it: The fact that you're both
willing to let it go, after having already invested a lot of time in it,
is a good sign for the language. Well done.
Hey Don, you speak my words. Specially that I can't see good reason for
T[new] with present
== Quote from Piotrek (star...@tlen.pl)'s article
dsimcha pisze:
3. An implementation I call StaticAA, which does not allow the addition or
removal of keys after it is constructed, but in exchange has almost zero
space
overhead and is very GC-efficient. It works by maintaining sorted
On 2009-10-19 19:34:04 +0200, Andrei Alexandrescu
seewebsiteforem...@erdani.org said:
Denis Koroskin wrote:
Put it simple: T[] is a range, and T[new] is a container. They belong
to different leagues.
Define ranges and define containers.
Yes, there is a lot common between them, because T[]
On 19/10/2009 19:10, BCS wrote:
Hello Yigal,
I think that Arrays and AAs need to be removed from the language. I
prefer to have a collections framework as part of Phobos without
special cases in the language for specific containers.
If it can be assured that all the current array ops will
will appear d3 ? What are the tasks ? it's not backward compatible
with D2 ? What major changes ?
when to stop adding new content of d2 ?
thank you very much to all
dolive
Andrei Alexandrescu wrote:
I just wrote this to Sean and Walter and subsequently discussed it with
Walter. Walter thinks this should work. Does anyone have the time and
inclination to test this out? It would involve hacking into druntime's
implementation of ~= (I'm not sure what the function
On 2009-10-19 21:53:53 +0200, Andrei Alexandrescu
seewebsiteforem...@erdani.org said:
dsimcha wrote:
== Quote from Andrei Alexandrescu (seewebsiteforem...@erdani.org)'s article
dsimcha wrote:
2. I don't understand how this solves the safety problem:
// foo lives on the heap b/c we've
Fawzi Mohamed fmoha...@mac.com wrote in message
news:hbhi5q$1gq...@digitalmars.com...
On 2009-10-18 20:01:26 +0200, language_fan f...@bar.com.invalid said:
Sun, 18 Oct 2009 16:35:53 +0200, Fawzi Mohamed thusly wrote:
on x86 the 64 bit extension added registers, that makes it faster, even
if
On 19/10/2009 21:20, dsimcha wrote:
== Quote from Jerry Quinn (jlqu...@optonline.net)'s article
dsimcha Wrote:
If anyone can think of any more, please let me know. Also, just thought of this
now: I wonder if it would make sense to use some polymorphism tricks (AA
operations are slow enough
Hello Yigal,
On 19/10/2009 19:10, BCS wrote:
Hello Yigal,
I think that Arrays and AAs need to be removed from the language. I
prefer to have a collections framework as part of Phobos without
special cases in the language for specific containers.
If it can be assured that all the current
== Quote from Yigal Chripun (yigal...@gmail.com)'s article
On 19/10/2009 21:20, dsimcha wrote:
== Quote from Jerry Quinn (jlqu...@optonline.net)'s article
dsimcha Wrote:
If anyone can think of any more, please let me know. Also, just thought
of this
now: I wonder if it would make
On Oct 20, 09 03:40, Piotrek wrote:
Bill Baxter pisze:
Just get rid of the the one-argument foreach over AAs altogether and
force
the user to be
explicit about it.
I wouldn't do so. Would anybody do an error by thinking that foreach
(elem,table) should iterate over keys?
Bearophile. And
On 19/10/2009 22:53, BCS wrote:
Hello Yigal,
On 19/10/2009 19:10, BCS wrote:
Hello Yigal,
I think that Arrays and AAs need to be removed from the language. I
prefer to have a collections framework as part of Phobos without
special cases in the language for specific containers.
If it can
On Mon, Oct 19, 2009 at 1:58 PM, KennyTM~ kenn...@gmail.com wrote:
On Oct 20, 09 03:40, Piotrek wrote:
Bill Baxter pisze:
Just get rid of the the one-argument foreach over AAs altogether and
force
the user to be
explicit about it.
I wouldn't do so. Would anybody do an error by thinking
dolive Wrote:
will appear d3 ? What are the tasks ? it's not backward compatible
with D2 ? What major changes ?
My understanding is that there will be a significant gap between the
finalization of D2 and the start of D3. Bartosz's ownership scheme may be part
of D3.
when to stop adding
1 - 100 of 183 matches
Mail list logo
