A summary of D's design principles

2010-09-15 Thread Andrei Alexandrescu
A coworker asked me where he could find a brief document of D's design principles. This was after I'd mentioned the "no function hijacking" stance. I think it would be a great idea if the up-and-coming www.d-programming-language.org contained such a document. Ideas for what it could contain?

Re: A summary of D's design principles

2010-10-21 Thread Bruno Medeiros
On 17/09/2010 23:39, retard wrote: Fri, 17 Sep 2010 14:33:30 -0700, Walter Bright wrote: retard wrote: FWIW, if you're picking up one of the most used languages out there, their list won't differ that much: Exactly. Much of that can be summed up as D being intended for professional productio

Re: A summary of D's design principles

2010-10-21 Thread Justin Johansson
On 21/10/2010 11:13 PM, Bruno Medeiros wrote: On 17/09/2010 23:39, retard wrote: Fri, 17 Sep 2010 14:33:30 -0700, Walter Bright wrote: retard wrote: FWIW, if you're picking up one of the most used languages out there, their list won't differ that much: Exactly. Much of that can be summed up

Re: A summary of D's design principles

2010-10-21 Thread retard
Thu, 21 Oct 2010 13:13:54 +0100, Bruno Medeiros wrote: > On 17/09/2010 23:39, retard wrote: >> Fri, 17 Sep 2010 14:33:30 -0700, Walter Bright wrote: >> >>> retard wrote: FWIW, if you're picking up one of the most used languages out there, their list won't differ that much: >>> >>> Exactl

Re: A summary of D's design principles

2010-10-21 Thread Justin Johansson
On 22/10/2010 12:26 AM, retard wrote: Thu, 21 Oct 2010 13:13:54 +0100, Bruno Medeiros wrote: On 17/09/2010 23:39, retard wrote: Fri, 17 Sep 2010 14:33:30 -0700, Walter Bright wrote: retard wrote: FWIW, if you're picking up one of the most used languages out there, their list won't differ th

Re: A summary of D's design principles

2010-10-21 Thread Bruno Medeiros
On 15/09/2010 18:58, Andrei Alexandrescu wrote: A coworker asked me where he could find a brief document of D's design principles. This was after I'd mentioned the "no function hijacking" stance. I think it would be a great idea if the up-and-coming www.d-programming-language.org contained such

Re: A summary of D's design principles

2010-10-21 Thread Bruno Medeiros
On 21/10/2010 14:28, Justin Johansson wrote: On 21/10/2010 11:13 PM, Bruno Medeiros wrote: On 17/09/2010 23:39, retard wrote: Fri, 17 Sep 2010 14:33:30 -0700, Walter Bright wrote: retard wrote: FWIW, if you're picking up one of the most used languages out there, their list won't differ that

Re: A summary of D's design principles

2010-10-21 Thread bearophile
Bruno Medeiros: > Rather, the big benefit of the statement above would be to reduce > certain wasteful discussions or comments that pop-up occasionally in > which someone proposes some "Pythonesque" change that might benefit > small programs but would be crap for medium/large ones. I suggest t

Re: A summary of D's design principles

2010-10-21 Thread Juanjo Alvarez
On Thu, 21 Oct 2010 15:26:14 +0100, Bruno Medeiros wrote: * And as for what D programmers think of other languages, well, it seems I guess D view of C++ could be rendered as an alcoholic father while D view of C++ would be a fashion victim son.

Re: A summary of D's design principles

2010-10-22 Thread Bruno Medeiros
On 21/10/2010 18:07, bearophile wrote: Bruno Medeiros: Rather, the big benefit of the statement above would be to reduce certain wasteful discussions or comments that pop-up occasionally in which someone proposes some "Pythonesque" change that might benefit small programs but would be crap for

Re: A summary of D's design principles

2010-09-15 Thread Simen kjaeraas
Andrei Alexandrescu wrote: A coworker asked me where he could find a brief document of D's design principles. This was after I'd mentioned the "no function hijacking" stance. I think it would be a great idea if the up-and-coming www.d-programming-language.org contained such a document.

Re: A summary of D's design principles

2010-09-15 Thread bearophile
Simen kjaeraas: > Easy things easy, difficult things possible. > > Safe before fast, but fast too. > > If it works in C, it works the same or not at all in D. > > Sugar is good for you, as is salt. In moderation. > > Too much power is not enough. (Where are my macros?!) > > Programmers are laz

Re: A summary of D's design principles

2010-09-15 Thread Simen kjaeraas
bearophile wrote: One of yours fixed: - If it works in C, it works (almost) the same or not at all in D. Mind giving examples to this one? I thought this was a big no-no. -- Simen

Re: A summary of D's design principles

2010-09-15 Thread dsimcha
== Quote from Andrei Alexandrescu (seewebsiteforem...@erdani.org)'s article > A coworker asked me where he could find a brief document of D's design > principles. This was after I'd mentioned the "no function hijacking" stance. > I think it would be a great idea if the up-and-coming > www.d-program

Re: A summary of D's design principles

2010-09-15 Thread Don
Andrei Alexandrescu wrote: A coworker asked me where he could find a brief document of D's design principles. This was after I'd mentioned the "no function hijacking" stance. I think it would be a great idea if the up-and-coming www.d-programming-language.org contained such a document. Idea

Re: A summary of D's design principles

2010-09-15 Thread bearophile
One more: If it runs, it may probably run at compile-time too. Bye, bearophile

Re: A summary of D's design principles

2010-09-15 Thread bearophile
Simen kjaeraas: > Mind giving examples to this one? I thought this was a big no-no. There are few silent differences, among them there are: - usage of global floating point variables/arrays that in some C programs are used without initialization, assuming they are set to zero. - fixed-sized arra

Re: A summary of D's design principles

2010-09-15 Thread Walter Bright
Simen kjaeraas wrote: bearophile wrote: One of yours fixed: - If it works in C, it works (almost) the same or not at all in D. Mind giving examples to this one? I thought this was a big no-no. I'm curious what bearophile is referring to, too. We've worked hard to ensure that C code either

Re: A summary of D's design principles

2010-09-15 Thread Nick Sabalausky
"Andrei Alexandrescu" wrote in message news:i6r1hn$2uu...@digitalmars.com... >A coworker asked me where he could find a brief document of D's design >principles. This was after I'd mentioned the "no function hijacking" >stance. > > I think it would be a great idea if the up-and-coming > www.d-

Re: A summary of D's design principles

2010-09-15 Thread Simen kjaeraas
bearophile wrote: Simen kjaeraas: Mind giving examples to this one? I thought this was a big no-no. There are few silent differences, among them there are: - usage of global floating point variables/arrays that in some C programs are used without initialization, assuming they are set to z

Re: A summary of D's design principles

2010-09-15 Thread Denis Koroskin
On Wed, 15 Sep 2010 23:36:48 +0400, Walter Bright wrote: Simen kjaeraas wrote: bearophile wrote: One of yours fixed: - If it works in C, it works (almost) the same or not at all in D. Mind giving examples to this one? I thought this was a big no-no. I'm curious what bearophile is refe

Re: A summary of D's design principles

2010-09-15 Thread Jesse Phillips
Nick Sabalausky Wrote: > - Make the "right" thing easy and the "wrong" thing hard. I believe that is "The easy way is the safe and correct way."

Re: A summary of D's design principles

2010-09-15 Thread Lars T. Kyllingstad
On Wed, 15 Sep 2010 22:19:26 +0200, Simen kjaeraas wrote: > bearophile wrote: > >> Simen kjaeraas: >> >>> Mind giving examples to this one? I thought this was a big no-no. >> >> There are few silent differences, among them there are: - usage of >> global floating point variables/arrays that in s

Re: A summary of D's design principles

2010-09-15 Thread bearophile
Simen kjaeraas: > The former could be seen as bad style, I think this is the relevant passage from the C Standard: Objects with static storage duration (3.7.1) shall be zero-initialized (8.5) before any other initialization takes place. Zero-initialization and initialization with a constan

Re: A summary of D's design principles

2010-09-15 Thread bearophile
Lars T. Kyllingstad: > This can be amended by requiring that fixed-size array parameters to > extern(C) functions be marked as 'ref'. > > See also: > http://d.puremagic.com/issues/show_bug.cgi?id=3604 Sometimes I translate some C code to D, in this case I have to watch for all the arrays, and u

Re: A summary of D's design principles

2010-09-15 Thread Jeff Nowakowski
On 09/15/2010 01:58 PM, Andrei Alexandrescu wrote: I know we discussed this once in the past, but couldn't find the discussion. Yeah, like 3 months ago: http://www.digitalmars.com/d/archives/digitalmars/D/The_design_principles_of_D_aka_The_D_Manifesto_111570.html

Re: A summary of D's design principles

2010-09-15 Thread Jonathan M Davis
On Wednesday, September 15, 2010 10:58:49 Andrei Alexandrescu wrote: > A coworker asked me where he could find a brief document of D's design > principles. This was after I'd mentioned the "no function hijacking" > stance. > > I think it would be a great idea if the up-and-coming > www.d-programmi

Re: A summary of D's design principles

2010-09-15 Thread Walter Bright
Denis Koroskin wrote: On Wed, 15 Sep 2010 23:36:48 +0400, Walter Bright wrote: Simen kjaeraas wrote: bearophile wrote: One of yours fixed: - If it works in C, it works (almost) the same or not at all in D. Mind giving examples to this one? I thought this was a big no-no. I'm curious w

Re: A summary of D's design principles

2010-09-16 Thread Justin Johansson
On 16/09/2010 7:17 AM, Jeff Nowakowski wrote: On 09/15/2010 01:58 PM, Andrei Alexandrescu wrote: I know we discussed this once in the past, but couldn't find the discussion. Yeah, like 3 months ago: http://www.digitalmars.com/d/archives/digitalmars/D/The_design_principles_of_D_aka_The_D_Mani

Re: A summary of D's design principles

2010-09-16 Thread Simen Kjaeraas
Here's a draft of something I'd like to see. I like having the ten commandments, with #0 not really counting. C&C welcome. == The D Manifesto == 0. Pragmatism is king. 1. Safe before all, fast before the rest. 2. High level where possible, low level where necessary. 3

Re: A summary of D's design principles

2010-09-16 Thread Justin Johansson
On 16/09/2010 8:34 PM, Simen Kjaeraas wrote: Here's a draft of something I'd like to see. I like having the ten commandments, with #0 not really counting. C&C welcome. == The D Manifesto == I'm really pleased that the word "Manifesto" is gradually making its way int

Re: A summary of D's design principles

2010-09-16 Thread Jeff Nowakowski
On 09/16/2010 09:51 AM, Justin Johansson wrote: I'm really pleased that the word "Manifesto" is gradually making its way into this ng. Not to be confused with The Third Manifesto, which describes the D database language. http://en.wikipedia.org/wiki/The_Third_Manifesto http://en.wikipedia.o

Re: A summary of D's design principles

2010-09-16 Thread Justin Johansson
On 16/09/2010 11:24 PM, Jeff Nowakowski wrote: On 09/16/2010 09:51 AM, Justin Johansson wrote: I'm really pleased that the word "Manifesto" is gradually making its way into this ng. Not to be confused with The Third Manifesto, which describes the D database language. http://en.wikipedia.org/

Re: A summary of D's design principles

2010-09-16 Thread Nick Sabalausky
"Simen Kjaeraas" wrote in message news:i6stke$o0...@digitalmars.com... > > 15. We're consenting adults, not suicidal maniacs. > Heh, I love this one :)

Re: A summary of D's design principles

2010-09-16 Thread Philippe Sigaud
On Thu, Sep 16, 2010 at 21:17, Nick Sabalausky wrote: > "Simen Kjaeraas" wrote in message > news:i6stke$o0...@digitalmars.com... > > > > 15. We're consenting adults, not suicidal maniacs. > > > > Heh, I love this one :) > > > That's the 10 commandments in hexadecimal, from 0 to F :-) That could

Re: A summary of D's design principles

2010-09-16 Thread Simen kjaeraas
On Thu, 16 Sep 2010 15:54:26 +0200, Jeff Nowakowski wrote: On 09/16/2010 09:51 AM, Justin Johansson wrote: I'm really pleased that the word "Manifesto" is gradually making its way into this ng. Not to be confused with The Third Manifesto, which describes the D database language. http:

Re: A summary of D's design principles

2010-09-16 Thread bearophile
Simen kjaeraas: > So ours should be The Fourth Manifesto, then? Mars Zen :-) Bye, bearophile

Re: A summary of D's design principles

2010-09-16 Thread sybrandy
On 09/16/2010 07:04 AM, Simen Kjaeraas wrote: Here's a draft of something I'd like to see. I like having the ten commandments, with #0 not really counting. C&C welcome. == The D Manifesto == 0. Pragmatism is king. 1. Safe before all, fast before the rest. 2. High le

Re: A summary of D's design principles

2010-09-17 Thread Walter Bright
Andrei Alexandrescu wrote: A coworker asked me where he could find a brief document of D's design principles. This was after I'd mentioned the "no function hijacking" stance. I think it would be a great idea if the up-and-coming www.d-programming-language.org contained such a document. I ag

Re: A summary of D's design principles

2010-09-17 Thread Jonathan M Davis
On Friday 17 September 2010 00:02:36 Walter Bright wrote: > Andrei Alexandrescu wrote: > > A coworker asked me where he could find a brief document of D's design > > principles. This was after I'd mentioned the "no function hijacking" > > stance. > > > > I think it would be a great idea if the up-

Re: A summary of D's design principles

2010-09-17 Thread F. Almeida
I would like such a manifesto to emphasize the following aspects that together, make D unique IMO: * Programs may be as high or as low level as the programmer chooses. * No single style is imposed on the programmer. * The memory can be managed automatically or manually.

Re: A summary of D's design principles

2010-09-17 Thread Nick B
On 16/09/2010 5:58 a.m., Andrei Alexandrescu wrote: A coworker asked me where he could find a brief document of D's design principles. This was after I'd mentioned the "no function hijacking" stance. there is no one, true, only to be used, library. D supports diversity.

Re: A summary of D's design principles

2010-09-17 Thread Justin Johansson
On 17/09/2010 6:48 PM, Nick B wrote: On 16/09/2010 5:58 a.m., Andrei Alexandrescu wrote: A coworker asked me where he could find a brief document of D's design principles. This was after I'd mentioned the "no function hijacking" stance. there is no one, true, only to be used, library. D suppo

Re: A summary of D's design principles

2010-09-17 Thread retard
Thu, 16 Sep 2010 21:38:24 -0400, sybrandy wrote: > On 09/16/2010 07:04 AM, Simen Kjaeraas wrote: >> Here's a draft of something I'd like to see. I like having the ten >> commandments, with #0 not really counting. C&C welcome. FWIW, if you're picking up one of the most used languages out there, t

Re: A summary of D's design principles

2010-09-17 Thread retard
Fri, 17 Sep 2010 21:18:04 +1200, Nick B wrote: > On 16/09/2010 5:58 a.m., Andrei Alexandrescu wrote: >> A coworker asked me where he could find a brief document of D's design >> principles. This was after I'd mentioned the "no function hijacking" >> stance. >> >> > there is no one, true, only to b

Re: A summary of D's design principles

2010-09-17 Thread Justin Johansson
On 17/09/2010 10:14 PM, retard wrote: 12. The tool does not pick you - you pick the tool. D developer's IQ> 90 ? 15. We're consenting adults, not suicidal maniacs. Some future directions for the newsgroup discussion? I don't think you should have even dignified the OP's post with a resp

Re: A summary of D's design principles

2010-09-17 Thread Jacob Carlborg
On 2010-09-17 03:38, sybrandy wrote: On 09/16/2010 07:04 AM, Simen Kjaeraas wrote: Here's a draft of something I'd like to see. I like having the ten commandments, with #0 not really counting. C&C welcome. == The D Manifesto == 0. Pragmatism is king. 1. Safe before all, fast before the rest.

Re: A summary of D's design principles

2010-09-17 Thread #ponce
> I would like such a manifesto to emphasize the following aspects that > together, make D unique IMO: > > * Programs may be as high or as low level as the programmer chooses. > * No single style is imposed on the programmer. > * The memory can be managed automatically or manually. Pragmatism not

Re: A summary of D's design principles

2010-09-17 Thread Gary Whatmore
retard Wrote: > Thu, 16 Sep 2010 21:38:24 -0400, sybrandy wrote: > > > On 09/16/2010 07:04 AM, Simen Kjaeraas wrote: > >> Here's a draft of something I'd like to see. I like having the ten > >> commandments, with #0 not really counting. C&C welcome. > > FWIW, if you're picking up one of the most

Re: A summary of D's design principles

2010-09-17 Thread Russel Winder
On Fri, 2010-09-17 at 09:36 -0400, Gary Whatmore wrote: [ . . . ] I assume you are just trolling, but for the record . . . > Haskell is just stupid. Their waisting they're time! It's brainwash Haskell is far from stupid. You may not like it, but saying it is stupid is in itself just stupid. [

Re: A summary of D's design principles

2010-09-17 Thread BLS
On 15/09/2010 19:58, Andrei Alexandrescu wrote: A coworker asked me where he could find a brief document of D's design principles. to reduce it to the max. The AnDrei design principles ;] no, just kidding. Seriously I wish we could use D2 for our dot net development tasks. Guess we could sa

Re: A summary of D's design principles

2010-09-17 Thread Walter Bright
retard wrote: FWIW, if you're picking up one of the most used languages out there, their list won't differ that much: Exactly. Much of that can be summed up as D being intended for professional production use, rather than: 1. a teaching tool (Pascal) 2. a research project (Haskell) 3. being

Re: A summary of D's design principles

2010-09-17 Thread retard
Fri, 17 Sep 2010 14:33:30 -0700, Walter Bright wrote: > retard wrote: >> FWIW, if you're picking up one of the most used languages out there, >> their list won't differ that much: > > Exactly. Much of that can be summed up as D being intended for > professional production use, rather than: > > 1

Re: A summary of D's design principles

2010-09-17 Thread Justin Johansson
On 18/09/2010 8:09 AM, retard wrote: Fri, 17 Sep 2010 14:33:30 -0700, Walter Bright wrote: retard wrote: FWIW, if you're picking up one of the most used languages out there, their list won't differ that much: Exactly. Much of that can be summed up as D being intended for professional product

Re: A summary of D's design principles

2010-09-17 Thread Nick B
On 18/09/2010 12:46 a.m., retard wrote: Fri, 17 Sep 2010 21:18:04 +1200, Nick B wrote: On 16/09/2010 5:58 a.m., Andrei Alexandrescu wrote: A coworker asked me where he could find a brief document of D's design principles. This was after I'd mentioned the "no function hijacking" stance. ther

Re: A summary of D's design principles

2010-09-17 Thread sybrandy
Concurrency is currently far from easy. Perhaps, but with D providing a message-passing API, we're certainly on our way to making it much easier. I tried Perl threading a few years ago and settled on using fork for what I needed as it was much easier. I later learned Erlang and went "Wow,

Re: A summary of D's design principles

2010-09-17 Thread sybrandy
On 09/17/2010 05:33 PM, Walter Bright wrote: retard wrote: FWIW, if you're picking up one of the most used languages out there, their list won't differ that much: Exactly. Much of that can be summed up as D being intended for professional production use, rather than: 1. a teaching tool (Pasca

Re: A summary of D's design principles

2010-09-17 Thread Nick B
On 18/09/2010 12:28 a.m., Justin Johansson wrote: On 17/09/2010 6:48 PM, Nick B wrote: On 16/09/2010 5:58 a.m., Andrei Alexandrescu wrote: A coworker asked me where he could find a brief document of D's design principles. This was after I'd mentioned the "no function hijacking" stance. there

Re: A summary of D's design principles

2010-09-17 Thread Jonathan M Davis
On Friday 17 September 2010 19:20:20 Nick B wrote: > On 18/09/2010 12:28 a.m., Justin Johansson wrote: > > On 17/09/2010 6:48 PM, Nick B wrote: > >> On 16/09/2010 5:58 a.m., Andrei Alexandrescu wrote: > >>> A coworker asked me where he could find a brief document of D's design > >>> principles. Thi

Re: A summary of D's design principles

2010-09-17 Thread retard
Fri, 17 Sep 2010 19:31:35 -0700, Jonathan M Davis wrote: > On Friday 17 September 2010 19:20:20 Nick B wrote: >> On 18/09/2010 12:28 a.m., Justin Johansson wrote: >> > On 17/09/2010 6:48 PM, Nick B wrote: >> >> On 16/09/2010 5:58 a.m., Andrei Alexandrescu wrote: >> >>> A coworker asked me where he

Re: A summary of D's design principles

2010-09-17 Thread Russel Winder
On Fri, 2010-09-17 at 14:33 -0700, Walter Bright wrote: > retard wrote: > > FWIW, if you're picking up one of the most used languages out there, > > their list won't differ that much: > > Exactly. Much of that can be summed up as D being intended for professional > production use, rather than: >

Re: A summary of D's design principles

2010-09-18 Thread Walter Bright
Russel Winder wrote: On Fri, 2010-09-17 at 14:33 -0700, Walter Bright wrote: retard wrote: FWIW, if you're picking up one of the most used languages out there, their list won't differ that much: Exactly. Much of that can be summed up as D being intended for professional production use, rather

Re: A summary of D's design principles

2010-09-18 Thread retard
Sat, 18 Sep 2010 03:44:30 -0700, Walter Bright wrote: > Russel Winder wrote: >> On Fri, 2010-09-17 at 14:33 -0700, Walter Bright wrote: >>> retard wrote: FWIW, if you're picking up one of the most used languages out there, their list won't differ that much: >>> Exactly. Much of that can

Re: A summary of D's design principles

2010-09-18 Thread retard
Sat, 18 Sep 2010 03:44:30 -0700, Walter Bright wrote: > I know nothing about Alice. You SHOULD probably study the ML family of languages a bit more closely. It feels like we're having a conversation with a dinosaur. After all, in the functional programming world, ML languages are the closest c

Re: A summary of D's design principles

2010-09-18 Thread dsimcha
== Quote from retard (r...@tard.com.invalid)'s article > >>> 2. a research project (Haskell) > >> > >> Haskell stopped being a research project many years ago, Haskell > >> development now happens in companies (including Microsoft) as much as > >> in universities and is about creating good examples

Re: A summary of D's design principles

2010-09-18 Thread retard
Sat, 18 Sep 2010 15:59:24 +, dsimcha wrote: > == Quote from retard (r...@tard.com.invalid)'s article >> >>> 2. a research project (Haskell) >> >> >> >> Haskell stopped being a research project many years ago, Haskell >> >> development now happens in companies (including Microsoft) as much >> >

Re: A summary of D's design principles

2010-09-18 Thread Lutger
retard wrote: > Sat, 18 Sep 2010 03:44:30 -0700, Walter Bright wrote: > >> I know nothing about Alice. > > You SHOULD probably study the ML family of languages a bit more closely. > It feels like we're having a conversation with a dinosaur. > > After all, in the functional programming world, ML

Re: A summary of D's design principles

2010-09-18 Thread Lutger
Andrei Alexandrescu wrote: > A coworker asked me where he could find a brief document of D's design > principles. This was after I'd mentioned the "no function hijacking" stance. > > I think it would be a great idea if the up-and-coming > www.d-programming-language.org contained such a document.

Re: A summary of D's design principles

2010-09-18 Thread retard
Sat, 18 Sep 2010 18:43:45 +0200, Lutger wrote: > retard wrote: > >> Sat, 18 Sep 2010 03:44:30 -0700, Walter Bright wrote: >> >>> I know nothing about Alice. >> >> You SHOULD probably study the ML family of languages a bit more >> closely. It feels like we're having a conversation with a dinosau

Re: A summary of D's design principles

2010-09-18 Thread Andrei Alexandrescu
On 09/18/2010 12:31 PM, retard wrote: Sat, 18 Sep 2010 18:43:45 +0200, Lutger wrote: retard wrote: Sat, 18 Sep 2010 03:44:30 -0700, Walter Bright wrote: I know nothing about Alice. You SHOULD probably study the ML family of languages a bit more closely. It feels like we're having a conver

Re: A summary of D's design principles

2010-09-18 Thread Walter Bright
Walter Bright wrote: C wasn't designed around a single paradigm, either, it was intended as a general purpose language, and was specifically not designed for any particular area of application (so says K&R). One example of C not being a particular paradigm is that it included modern (for the

Re: A summary of D's design principles

2010-09-18 Thread Walter Bright
retard wrote: Yes, Pascal WAS a teaching language. However, probably there are no colleges using it these days. Teachers have adopted more recent languages during the last 20 years and it makes no sense to compare anything to Pascal anymore. I meant it as an example of a language that was des

Re: A summary of D's design principles

2010-09-18 Thread Walter Bright
retard wrote: It feels like we're having a conversation with a dinosaur. I apologize for all my numerous shortcomings!

Re: A summary of D's design principles

2010-09-18 Thread retard
Sat, 18 Sep 2010 11:45:51 -0700, Walter Bright wrote: > retard wrote: >> It feels like we're having a conversation with a dinosaur. > > I apologize for all my numerous shortcomings! I'm sorry :-) But I still recommend writing couple of hundreds of lines of code in some ML. It's a great experien

Re: A summary of D's design principles

2010-09-18 Thread JimBob
"retard" wrote in message news:i73350$2m0...@digitalmars.com... > Sat, 18 Sep 2010 11:45:51 -0700, Walter Bright wrote: > >> retard wrote: >>> It feels like we're having a conversation with a dinosaur. >> >> I apologize for all my numerous shortcomings! > > I'm sorry :-) But I still recommend wr

Re: A summary of D's design principles

2010-09-18 Thread retard++
> If I'd write > something significant commercial code in any functional language, I might > choose F# or Haskell instead. Have you ever written something significant ?

Re: A summary of D's design principles

2010-09-18 Thread retarded.clear()
retard++ Wrote: > > If I'd write > > something significant commercial code in any functional language, I might > > choose F# or Haskell instead. > > Have you ever written something significant ? > The douchebag has never done anything. Trolling here day and night. Doesn't know anything about

Re: A summary of D's design principles

2010-09-18 Thread Jonathan M Davis
On Saturday 18 September 2010 11:43:36 Walter Bright wrote: > >> Basic is famous in that its charter specifically was for > >> non-programmers. Cobol was designed for managers to be able to > >> understand the code, not to write it (a slightly different aim). > > > > Both Basic and Cobol are dead

Re: A summary of D's design principles

2010-09-18 Thread Jonathan M Davis
On Saturday 18 September 2010 08:59:24 dsimcha wrote: > == Quote from retard (r...@tard.com.invalid)'s article > > > >>> 2. a research project (Haskell) > > >> > > >> Haskell stopped being a research project many years ago, Haskell > > >> development now happens in companies (including Microsoft)

Re: A summary of D's design principles

2010-09-18 Thread Simen kjaeraas
Walter Bright wrote: True, but irrelevant to my point. I see that nobody understood my point at all. I'm sure I'm not the only with my palm glued to my face from the replies you got. -- Simen

Re: A summary of D's design principles

2010-09-18 Thread Walter Bright
Jonathan M Davis wrote: On Saturday 18 September 2010 11:43:36 Walter Bright wrote: Basic is famous in that its charter specifically was for non-programmers. Cobol was designed for managers to be able to understand the code, not to write it (a slightly different aim). Both Basic and Cobol are d

Re: A summary of D's design principles

2010-09-18 Thread JMRyan
Simen Kjaeraas wrote in news:i6stke$o0v$1 @digitalmars.com: > Here's a draft of something I'd like to see. I like having the ten > commandments, with #0 not really counting. C&C welcome. > > == The D Manifesto == > Please don't call it a manifesto. A statement of des

Re: A summary of D's design principles

2010-09-18 Thread Simen kjaeraas
JMRyan wrote: Simen Kjaeraas wrote in news:i6stke$o0v$1 @digitalmars.com: Here's a draft of something I'd like to see. I like having the ten commandments, with #0 not really counting. C&C welcome. == The D Manifesto == Please don't call it a manifesto. A statem

Re: A summary of D's design principles

2010-09-19 Thread Jonathan M Davis
On Saturday 18 September 2010 23:47:09 Simen kjaeraas wrote: > JMRyan wrote: > > Simen Kjaeraas wrote in news:i6stke$o0v$1 > > > > @digitalmars.com: > >> Here's a draft of something I'd like to see. I like having the ten > >> commandments, with #0 not really counting. C&C welcome. > >> > >>

Re: A summary of D's design principles

2010-09-19 Thread Justin Johansson
On 19/09/2010 7:20 AM, retard++ wrote: If I'd write something significant commercial code in any functional language, I might choose F# or Haskell instead. Have you ever written something significant ? Here's a significant challenge. Try implementing the XPath 2.0 XDM data model in D and se

Re: A summary of D's design principles

2010-09-19 Thread Justin Johansson
On 19/09/2010 2:59 AM, Lutger wrote: To me some of the most distinguishing aspects of D are: - scale to complex as well as small programs: unlike C# and Java but perhaps like python - focus on early binding: this quote from David Griers is fitting: "Never put off until run time what you can do

Re: A summary of D's design principles

2010-09-19 Thread Justin Johansson
On 19/09/2010 7:41 AM, retarded.clear() wrote: retard++ Wrote: If I'd write something significant commercial code in any functional language, I might choose F# or Haskell instead. Have you ever written something significant ? The douchebag has never done anything. Trolling here day and nigh

Re: A summary of D's design principles

2010-09-19 Thread Lutger
Justin Johansson wrote: > On 19/09/2010 2:59 AM, Lutger wrote: >> To me some of the most distinguishing aspects of D are: >> >> - scale to complex as well as small programs: unlike C# and Java but perhaps >> like python >> >> - focus on early binding: this quote from David Griers is fitting: "Neve

Re: A summary of D's design principles

2010-09-19 Thread Justin Johansson
On 19/09/2010 11:49 PM, Lutger wrote: Justin Johansson wrote: On 19/09/2010 2:59 AM, Lutger wrote: To me some of the most distinguishing aspects of D are: - scale to complex as well as small programs: unlike C# and Java but perhaps like python - focus on early binding: this quote from David

Re: A summary of D's design principles

2010-09-19 Thread lurker
Justin Johansson Wrote: > On 19/09/2010 11:49 PM, Lutger wrote: > > Justin Johansson wrote: > > > >> On 19/09/2010 2:59 AM, Lutger wrote: > >>> To me some of the most distinguishing aspects of D are: > >>> > >>> - scale to complex as well as small programs: unlike C# and Java but > >>> perhaps >

Re: A summary of D's design principles

2010-09-19 Thread Andrei Alexandrescu
On 9/19/10 9:04 CDT, Justin Johansson wrote: To be well read on the subject of OOP models I can recommend this link to a well-articulated paper by Bertrand Meyer: http://se.ethz.ch/~meyer/publications/computer/taxonomy.pdf I don't consider that piece a recommendable read for contemporary OOP

Re: A summary of D's design principles

2010-09-19 Thread Walter Bright
Justin Johansson wrote: Some of these features you mention are very worthwhile but I mean that that D does not offer any better OOP system amongst its contemporary rivals. To be well read on the subject of OOP models I can recommend this link to a well-articulated paper by Bertrand Meyer: http:

Re: A summary of D's design principles

2010-09-19 Thread JMRyan
One thing that seems to have been missed in this discussion: minimize (or at least reduce from C++ levels) undefined behavior. That's the reason for auto-initialized variables. It's not to provide aconvenience for those times when the default values are what you want. It's so that failure to

Re: A summary of D's design principles

2010-09-19 Thread Walter Bright
JMRyan wrote: One thing that seems to have been missed in this discussion: minimize (or at least reduce from C++ levels) undefined behavior. That's the reason for auto-initialized variables. It's not to provide aconvenience for those times when the default values are what you want. It's so

Re: A summary of D's design principles

2010-09-20 Thread Jérôme M. Berger
> True, but irrelevant to my point. I see that nobody understood my point at > all. I am appalled at the way some people here seem unable to understand basic sentences both in this thread and others (and it's not just a question of not being native English speakers, I'm not either). I'm s

Re: A summary of D's design principles

2010-09-20 Thread Jay Byrd
On Sat, 18 Sep 2010 19:15:44 +, retard wrote: > Sat, 18 Sep 2010 11:45:51 -0700, Walter Bright wrote: > >> retard wrote: >>> It feels like we're having a conversation with a dinosaur. >> >> I apologize for all my numerous shortcomings! > > I'm sorry :-) But I still recommend writing couple

Re: A summary of D's design principles

2010-09-20 Thread Jay Byrd
On Fri, 17 Sep 2010 15:08:07 +0200, Jacob Carlborg wrote: > On 2010-09-17 03:38, sybrandy wrote: >> On 09/16/2010 07:04 AM, Simen Kjaeraas wrote: >>> Here's a draft of something I'd like to see. I like having the ten >>> commandments, with #0 not really counting. C&C welcome. >>> >>> == The D Mani

Re: A summary of D's design principles

2010-09-20 Thread Jay Byrd
On Sun, 19 Sep 2010 06:33:28 +, JMRyan wrote: > Simen Kjaeraas wrote in news:i6stke$o0v$1 > @digitalmars.com: > >> Here's a draft of something I'd like to see. I like having the ten >> commandments, with #0 not really counting. C&C welcome. >> >> == The D Manifesto

Re: A summary of D's design principles

2010-09-20 Thread hismastersvoice
Jay Byrd Wrote: > On Sat, 18 Sep 2010 19:15:44 +, retard wrote: > > > Sat, 18 Sep 2010 11:45:51 -0700, Walter Bright wrote: > > > >> retard wrote: > >>> It feels like we're having a conversation with a dinosaur. > >> > >> I apologize for all my numerous shortcomings! > > > > I'm sorry :-)

Re: A summary of D's design principles

2010-09-20 Thread Jay Byrd
On Sat, 18 Sep 2010 14:20:20 +1200, Nick B wrote: > On 18/09/2010 12:28 a.m., Justin Johansson wrote: >> On 17/09/2010 6:48 PM, Nick B wrote: >>> On 16/09/2010 5:58 a.m., Andrei Alexandrescu wrote: A coworker asked me where he could find a brief document of D's design principles. This wa

  1   2   >