@asmeurer, I respectfully disagree. Using a python file to represent the grammar forces the user to understand and know the format of the file. Also, should the current Parser generator Framework needs be replaced in future (discontinued or any similar reason), it would cause much inconvenience, because then the users would have to learn about the new format by which the grammar is specified. Such an arrangement (the one that you are suggesting), breaks the API in such an event. Plus, if we specify the grammar as I have mentioned in the proposal, it allows the user to directly use EBNF (Extended Backus-Naur Form) which is a standard way to represent CFGs (Context Free Grammars). I hope this justifies my using such an arrangement.
Regards, Aditya -- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sympy. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/682827be-7367-4f6a-a7f7-9e65d6dbb491%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
