Georg Brandl wrote:
> Adam Olsen schrieb:
>
>>Another example is the use of BNF, which although dominant in its
>>field, it provides a steep learning curve for most programmers.
>
> We could of course accompany each BNF-described item with an example.
An alternative to BNF would be syntax diagram
Adam Olsen wrote:
> The term "Displays" is pretty obscure as well,
Hmmm, I'd call them "constructor expressions" or some such.
--
Greg
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
ht
Adam Olsen schrieb:
>> I don't pretend to be speaking for anyone else, but I'd be surprised
>> if I were unique.
>
> Your experiences *shouldn't* be unique, but I'm afraid they might be.
> Another example is the use of BNF, which although dominant in its
> field, it provides a steep learning cu
On Tue, Mar 4, 2008 at 8:03 PM, Stephen J. Turnbull <[EMAIL PROTECTED]> wrote:
> Adam Olsen writes:
> > On Tue, Mar 4, 2008 at 3:13 PM, Stephen J. Turnbull <[EMAIL PROTECTED]>
> wrote:
>
> > > I would like to see the clear division between the language (ie,
> > > the syntax) and the built-in
Adam Olsen writes:
> On Tue, Mar 4, 2008 at 3:13 PM, Stephen J. Turnbull <[EMAIL PROTECTED]>
> wrote:
> > I would like to see the clear division between the language (ie,
> > the syntax) and the built-in functionality maintained. I'm not
> > sure I like the proposed title for that reason.
On Tue, Mar 4, 2008 at 5:04 PM, Steve Holden <[EMAIL PROTECTED]> wrote:
> Greg Ewing wrote:
> > Adam Olsen wrote:
> >> Such a division would make it unnecessarily hard to find documentation
> >> on True, False, None, etc. They've become keywords for pragmatic
> >> purposes (to prevent accident
Greg Ewing wrote:
> Adam Olsen wrote:
>> Such a division would make it unnecessarily hard to find documentation
>> on True, False, None, etc. They've become keywords for pragmatic
>> purposes (to prevent accidental modification), not because we think
>> they ideally should be syntax instead of bui
Adam Olsen wrote:
> Such a division would make it unnecessarily hard to find documentation
> on True, False, None, etc. They've become keywords for pragmatic
> purposes (to prevent accidental modification), not because we think
> they ideally should be syntax instead of builtins.
Maybe the soluti
On Tue, Mar 4, 2008 at 3:13 PM, Stephen J. Turnbull <[EMAIL PROTECTED]> wrote:
> Georg Brandl writes:
> > You speak my mind. For ages I've wanted to put the builtins together with
> > the language reference into a new document called "Python Core Language".
> > I've just never had the time to
