The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 |
From: George Sakkis <george.sak...@gmail.com>
Date: Wed, 13 May 2009 11:29:44 -0400
Local: Wed, May 13 2009 11:29 am
Subject: Re: [Python-ideas] Default arguments in Python - the return - running out of ideas but...
On Wed, May 13, 2009 at 10:52 AM, Jeremy Banks <jer...@jeremybanks.ca> wrote: Traditionally, keywords are recognized at the lexer level, which then > To someone who's a novice to this, could someone explain to me why it > has to be an existing keyword at all? Since not identifiers are valid > in that context anyway, why couldn't it be a new keyword that can > still be used as an identifier in valid contexts? For example (not > that I advocate this choice of keyword at all): > def foo(bar reinitialize_default []): # <-- it's a keyword here > That would be a syntax error now and if it were defined as a keyword > Is there a reason that this wouldn't be a viable approach? passes tokens to the parser. Lexers are pretty simple (typically constants and regular expressions) and don't take the context into account. In principle what you're saying could work, but given the significant reworking of the lexer/parser it would require, it's quite unlikely to happen, for better or for worse. George You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
| |||||||||||||