Re^2: (OT) Yapp rules and resolving reduce/reduce errors

That's the solution I'm using, but it means that any change to how database_ident is defined needs to be propagated by hand. Isn't there a way of saying "In the case of a reduce/reduce conflict, resolve in this fashion." ?

My criteria for good software:

Does it work?
Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

Comment on Re^2: (OT) Yapp rules and resolving reduce/reduce errors

Replies are listed 'Best First'.
Re^3: (OT) Yapp rules and resolving reduce/reduce errors by ikegami (Patriarch) on Apr 11, 2008 at 00:08 UTC
No idea. I don't know anything about Yapp (or yacc, for that matter). If you really think `database_ident` is likely to change, you could go with: `database_ident: ident ; table_ident: ident ; column_ident: ident ; qualified_database_ident: database_ident ; qualified_table_ident: database_ident '.' table_ident \| table_ident ; qualified_column_ident: database_ident '.' table_ident '.' column_ident \| table_ident '.' column_ident \| column_ident ;` [download]	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^3: (OT) Yapp rules and resolving reduce/reduce errors
by ikegami (Patriarch) on Apr 11, 2008 at 00:08 UTC

No idea. I don't know anything about Yapp (or yacc, for that matter). If you really think database_ident is likely to change, you could go with:

database_ident:
    ident
;

table_ident:
    ident
;

column_ident:
    ident
;

qualified_database_ident:
    database_ident
;

qualified_table_ident:
    database_ident '.' table_ident
  |                    table_ident
;

qualified_column_ident:
    database_ident '.' table_ident '.' column_ident
  |                    table_ident '.' column_ident
  |                                    column_ident
;
[download]

[reply]
[d/l]
[select]