Nick Sabalausky wrote:
I was assuming he meant cost of implementing that feature, but maybe you're
right...?
I meant the cost to the user.
"bearophile" wrote in message
news:hkv7u7$1a3...@digitalmars.com...
> Walter Bright:
>
> [about non-nullable types]
>> It's a benefit/cost issue. There are no bug-preventing features that are
>> without cost, the idea is to maximize the ratio.
>
> It surely has a cost (you can see it in the Cyclo
Nick Sabalausky wrote:
Real-world example that's actually happened to me far too many times (and
has *never* happened to me in any language other than D):
I'm writing app A and library B, both of which depend on an external library
C. I compile A/B with -w to check for any warnings in my code.
On 2010-02-10 22:54:40 -0500, Ary Borenszweig said:
Ary Borenszweig wrote:
Michel Fortin wrote:
unittest {
NonNullable!Object o;
Here o is null.
Sorry, just read the class comments. But if this can't be implemented
without compiler support... then it's not of much use. :-(
To recap
Ary Borenszweig wrote:
Michel Fortin wrote:
unittest {
NonNullable!Object o;
Here o is null.
Sorry, just read the class comments. But if this can't be implemented
without compiler support... then it's not of much use. :-(
Michel Fortin wrote:
unittest {
NonNullable!Object o;
Here o is null.
NonNullable!ClassInfo o2 = o.classinfo;
NonNullable!TypeInfo o3;
//NonNullable!Object o4 = o2; // FIXME: polymorphic NonNullable
o = new Object;
o = o2;
try {
o = o3; // should throw
That's because only people who care about D would post comments there. The
other people, they just ignore this topic.
If you want to see comments that's not optimistic. Try posting something like:
"Wow, D is the best language ever"
Andrei Alexandrescu Wrote:
> The comments seem to be very optim
On 2010-02-10 17:29:09 -0500, Walter Bright said:
retard wrote:
What exactly is the cost here? The non-nullability invariant can be
checked on compile time. It incurs no runtime overhead. Also the
notation can be quite terse, as we have seen in Other Languages(tm).
If you want, you can crea
Nick Sabalausky wrote:
> (you can say "C should never release
> without fixing all warnings first" all you want, but the fact is: it still
> happens).
How would the author of C check against all possible warnings in all
possible versions of all possible D compilers, including future versions
of
Walter Bright wrote:
http://www.reddit.com/r/d_language/comments/b05yq/d_losing_momentum/
I'm not sure if I should vote the title up or down :o). I upvoted. The
comments seem to be very optimistic, which is remarkable given the mood
suggested by the question.
Andrei
Real-world example that's actually happened to me far too many times (and
has *never* happened to me in any language other than D):
I'm writing app A and library B, both of which depend on an external library
C. I compile A/B with -w to check for any warnings in my code. Either it has
warnings
http://www.reddit.com/r/d_language/comments/b05yq/d_losing_momentum/
retard wrote:
What exactly is the cost here? The non-nullability invariant can be
checked on compile time. It incurs no runtime overhead. Also the notation
can be quite terse, as we have seen in Other Languages(tm).
If you want, you can create a template NonNullable that wraps an
existing typ
Leandro Lucarella wrote:
This supposedly "safe" program under Mac OS X 10.6 doesn't give any error
neither at compile time nor at runtime, yet it isn't memory-safe at all as
it corrupts some part of the memory space.
@safe is in its infancy, and I expect there to be some gaps. We'll get
them
Walter Bright, el 10 de febrero a las 11:33 me escribiste:
> retard wrote:
> >Tue, 09 Feb 2010 18:49:31 -0800, Walter Bright wrote:
> >
> >>D has moved a lot towards supplying by default a lot of what Coverity
> >>claims to do. By making such an expensive tool irrelevant for D, we can
> >>make D mu
Wed, 10 Feb 2010 12:47:41 -0800, Walter Bright wrote:
> Nick Sabalausky wrote:
>> "Walter Bright" wrote in message
>> news:hkv1mg$s6...@digitalmars.com...
>>> retard wrote:
Tue, 09 Feb 2010 18:49:31 -0800, Walter Bright wrote:
> D has moved a lot towards supplying by default a lot o
Walter Bright:
[about non-nullable types]
> It's a benefit/cost issue. There are no bug-preventing features that are
> without cost, the idea is to maximize the ratio.
It surely has a cost (you can see it in the Cyclone language: it's safe but
quite fussy, so the costs for the programmer can be
"retard" wrote in message
news:hkv5op$s4...@digitalmars.com...
> Wed, 10 Feb 2010 15:29:06 -0500, Nick Sabalausky wrote:
>
>> "Walter Bright" wrote in message
>> news:hkv1mg$s6...@digitalmars.com...
>>>
>>> Yes, there have been a couple long threads about that. Dereferencing a
>>> null pointer i
Nick Sabalausky wrote:
"Walter Bright" wrote in message
news:hkv1mg$s6...@digitalmars.com...
retard wrote:
Tue, 09 Feb 2010 18:49:31 -0800, Walter Bright wrote:
D has moved a lot towards supplying by default a lot of what Coverity
claims to do. By making such an expensive tool irrelevant for
Wed, 10 Feb 2010 15:29:06 -0500, Nick Sabalausky wrote:
> "Walter Bright" wrote in message
> news:hkv1mg$s6...@digitalmars.com...
>> retard wrote:
>>> Tue, 09 Feb 2010 18:49:31 -0800, Walter Bright wrote:
>>>
D has moved a lot towards supplying by default a lot of what Coverity
claims t
"Walter Bright" wrote in message
news:hkv1mg$s6...@digitalmars.com...
> retard wrote:
>> Tue, 09 Feb 2010 18:49:31 -0800, Walter Bright wrote:
>>
>>> D has moved a lot towards supplying by default a lot of what Coverity
>>> claims to do. By making such an expensive tool irrelevant for D, we can
>
retard wrote:
Tue, 09 Feb 2010 18:49:31 -0800, Walter Bright wrote:
D has moved a lot towards supplying by default a lot of what Coverity
claims to do. By making such an expensive tool irrelevant for D, we can
make D much more cost effective.
D doesn't provide non-nullable types
Yes, there
Nick Sabalausky wrote:
On http://www.digitalmars.com/d/ : The top link in the left-panel (just
below the search box) that says "D 1.0 ->". I think it actually is the D1
page, but the header says in big letters "D Programming Language 2.0".
Ah, I see. The page *is* the 1.0 page, but my templat
Is this what you're looking for?
http://svn.dsource.org/projects/vsplugind/downloads/
Tue, 09 Feb 2010 18:49:31 -0800, Walter Bright wrote:
> D has moved a lot towards supplying by default a lot of what Coverity
> claims to do. By making such an expensive tool irrelevant for D, we can
> make D much more cost effective.
D doesn't provide non-nullable types and local refs can still
Sorry for posting at wrong place.
And thank you for your responses. I will try it and learn it !
Robert Jacques, el 10 de febrero a las 01:03 me escribiste:
> -Getting concurrent GC code correct is very hard. Boehm's algorithm,
> for instance, looks extremely racy.
There is a very simple concurrent GC model using fork()[1]. This is Unix only
though (and very dependent on how efficiently fork(
Michel Fortin Wrote:
> On 2010-02-10 05:02:10 -0500, Walter Bright said:
>
> > Mike James wrote:
> >> I've noticed that when you click on the D1 page selection it loads
> >> the D2 page. I think it need fixing. Or is it a global conspiracy to
> >> remove interest of D1 in favour of D2. I think w
On 2010-02-10 05:02:10 -0500, Walter Bright said:
Mike James wrote:
I've noticed that when you click on the D1 page selection it loads
the D2 page. I think it need fixing. Or is it a global conspiracy to
remove interest of D1 in favour of D2. I think we should be told. Oh,
the humanity... :-)
Walter Bright wrote:
bearophile wrote:
But there are many C++ programmers that don't use exceptions, for
example they are not allowed in Google C++ code:
http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml#Exceptions
So surely not 100% of D code will use exceptions. That's why I ha
"Michel Fortin" wrote in message
news:hkt3gq$19p...@digitalmars.com...
> On 2010-02-09 19:26:05 -0500, bearophile said:
>
>> Walter Bright:
>>> I don't know why Google proscribes exceptions,
>>
>> If you look at that link, and you click on the arrow, you will see a nice
>> list of pro-cons :-)
On 2/9/10 16:53, Steve Teale wrote:
When D2 is 'frozen', as a special treat would it be possible for it to be
able to generate object files that could be converted into shared
libraries, and for Phobos to be a shared library to support same.
I have tried every which way I can think of to create
Robert Jacques wrote:
Based on a thread on the DMD concurrency mailing list I've begun to get
a sinking regarding the future of the garbage collector in D: most of
the work in GC algorithms has gone into functional and (mostly) pure-OO
languages, leaving a multi-paradigm systems programming lan
On Wed, 10 Feb 2010 01:06:47 -0500, Andrei Alexandrescu
wrote:
Robert Jacques wrote:
Based on a thread on the DMD concurrency mailing list I've begun to get
a sinking regarding the future of the garbage collector in D: most of
the work in GC algorithms has gone into functional and (mostly
"Walter Bright" wrote in message
news:hku07e$1jg...@digitalmars.com...
> Mike James wrote:
>> I've noticed that when you click on the D1 page selection it loads
>> the D2 page. I think it need fixing. Or is it a global conspiracy to
>> remove interest of D1 in favour of D2. I think we should be t
Mike James wrote:
I've noticed that when you click on the D1 page selection it loads
the D2 page. I think it need fixing. Or is it a global conspiracy to
remove interest of D1 in favour of D2. I think we should be told. Oh,
the humanity... :-)
I couldn't reproduce this. Can you please tell me
I've noticed that when you click on the D1 page selection it loads the D2 page.
I think it need fixing. Or is it a global conspiracy to remove interest of D1
in favour of D2. I think we should be told. Oh, the humanity... :-)
-=mike=-
37 matches
Mail list logo
