Movatterモバイル変換

[Python-ideas] In call grammar, replace primary with possible_call? (was Re: ...quote followed by a left parenthesis...?)

• Previous message (by thread):[Python-ideas] In call grammar,replace primary with possible_call? (was Re: ...quote followed by aleft parenthesis...?)
• Next message (by thread):[Python-ideas] In call grammar, replace primary with possible_call? (was Re: ...quote followed by a left parenthesis...?)
• Messages sorted by:[ date ][ thread ][ subject ][ author ]

On 16 July 2015 at 05:18, Steven D'Aprano <steve at pearwood.info> wrote:> On Wed, Jul 15, 2015 at 07:03:50PM -0400, Terry Reedy wrote:>>> So here is the proposal: in the call definition, change primary to>>   possible_call ::= identifier | parenth_form | yield_atom>>                     | attributeref | subscription | slicing | call>>>> As for error messages, there is another thread suggesting that the>> messages for SyntexError might be vastly improved.>>> This sounds like a good proposal. +1Note that the proposal should also include a change to "call":call ::= possible_call '(' args ')'replacingcall  ::= primary '(' args ')'(I was initially confused by the fact that possible_call included callas an option, until I remembered how it fitted into the largerpicture).This seems to me like more complexity than is warranted, particularlyas the error message quality drops dramatically (unless we improve thesyntax error message at the same time).So I'm -0 on this.Paul

• Previous message (by thread):[Python-ideas] In call grammar,replace primary with possible_call? (was Re: ...quote followed by aleft parenthesis...?)
• Next message (by thread):[Python-ideas] In call grammar, replace primary with possible_call? (was Re: ...quote followed by a left parenthesis...?)
• Messages sorted by:[ date ][ thread ][ subject ][ author ]