Suppose a user has both <column name list> and column_name_list? In designing the interface I had to take things like that into account. A user is not likely to use both by design, but he might be transitioning from one style to another, or might have made an error. If it was an error silently overloading the two would make it very hard to debug. And if the scheme gets *too* complex, then it becomes difficult for a user to determine exactly what name they are going to get.
Trying to work out all this, I decided, given a choice between letting things get confusing, or throwing fatal errors, that I would, when it was a matter of doubt, prefer the fatal error. There are also some personal choices. The current scheme favors angle-bracketed names, which I like, but that would not be everyone's choice. On Thu, Nov 26, 2015 at 4:51 AM, Cev Ing <[email protected]> wrote: > > > Am Donnerstag, 26. November 2015 11:41:37 UTC+1 schrieb rns: >> >> Don't know exactly. One thing that comes to mind is that _ is then used >> to replace spaces in LHS, if any. >> As a possible workaround, angle brackets allow using a whitespace in >> symbol names, e.g. <create table> instead of create_table. >> > > Now I rewrote the grammar using angle brackets and I got exactly what I > intended to get before using underscores: > > bless( [ > bless( [ > 'id' > ], 'DDL::identifier' ) > ], 'DDL::column_name_list' ), > > The rule <column name list> gets blessed to column_name_list. > > This makes it even more questionable, why the rule can not be called > column_name_list. An underscore rule could be blessed directly without any > rewriting. > > -- > You received this message because you are subscribed to the Google Groups > "marpa parser" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "marpa parser" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
