didge wrote:
> For me, this is a robustness issue. Being tolerant is great, but not at the
> cost of robustness. But, being new here, I'm not sure what exactly what
> being tolerant means to you.
>
> Being tolerant, to me, means that users are free to use white space,
> indentation, grouping, quoting or blocking as it makes sense for their needs
> and tastes.
For me tolerance and robustness in this case are related. I prefer a
parser that doesn't exit in the mentioned cases. That doesn't exclude
a 'strict' option, as you propose (in your case the default).
> Disallowing extra punctuation in my humble opinion does not make OGDL any
> less tolerant according to my definition and makes OGDL more robust because
> OGDL without extra punctuation is easier to read and can't mask any
> potential errors.
One thing are extra commas, and another is () and ((a)). I think these
are part of the language as is (((1+2))) in a math expression. Anyway,
let the parsers evolve and w'll see what is more coherent.
--
Rolf.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click_______________________________________________
Ogdl-core mailing list
Ogdl-core@...
https://lists.sourceforge.net/lists/listinfo/ogdl-core
