Re: [Iverilog-devel] Is there any way to avoid this shift/reduce conflict?

[Evan L. <sa2...@cy...>]

On 09/01/2015 02:15, Pete Johnson wrote:

> modport master (input a, b, output c, d);

Ok - thanks for the example - my 'modports_port_list' example parse 
should therefore look like this:

input a, b, c, output d, e, f

this can always be parsed with one token of look-ahead as long as the 
lexer can distinguish between 'port_direction' and IDENTIFIER (it needs 
to do this when it reaches 'output', not ','). This begs the question of 
why it can't, which is what (2) in my last post was about.

-Evan