@Jo thanks for the swift reply. I'll try to explain my position to you. 
Since, I come from a bit theoretical background, I do prefer to use EBNF to 
manipulate grammars. As you said, that is a selected group of people and I 
believe that. Also, on the suggestion of @asmeurer, if you read 6th last 
post, you'd find that people wanting to work with Python can do so directly 
without bothering with explicit notation. Here I ask you one thing. I have 
seen the documentation of modgrammar and even Spark and while both of them 
use Python for directly represent the grammar, you'd find that without 
prior knowledge of EBNF, you cannot write the python code. It is because, 
they encapsulate the EBNF form by Python code and so I believe that EBNF 
should be known a priori. Plus, as you said no user is ever going to bother 
about XYZ-Sympy converters. That would rest on developers who set out to 
define those parsers. I do think that people who intend to create parsers, 
would have prior knowledge of EBNF. Even if they don't as you claim, they 
can always bypass that step entirely. As for the maintenance part, if 
modgrammar or any other PGF  decides to discontinue or change their API, we 
would have to only change the Spec to Language converter file or as you 
claim learn the new API. What I don't seem to understand is that, there are 
2 approaches to do the given thing and even if one is not widely popular ( 
as you claim), if we do add support for that, it would only serve to 
empower someone who fits in that particular case to use it. So where's the 
issue?

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/00f22cf5-df52-48d9-aa1f-cb111232b80b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to