Skip to content
This repository has been archived by the owner on Jan 31, 2024. It is now read-only.

Should CueParser use a formal grammar? #14

Open
GoogleCodeExporter opened this issue Jan 7, 2016 · 1 comment
Open

Should CueParser use a formal grammar? #14

GoogleCodeExporter opened this issue Jan 7, 2016 · 1 comment

Comments

@GoogleCodeExporter
Copy link

CueParser uses a custom parser. While flexible, this is error-prone and
hard to maintain. Perhaps it would be better to use a parser based on a
formal grammar.

This is an open issue. The solution was undecided at the moment this issue
was registered.

Original issue reported on code.google.com by [email protected] on 11 May 2008 at 8:12

@GoogleCodeExporter
Copy link
Author

An argument against using a formal grammar is that, by necessity, it would have 
to be
relatively general due to the forgiving nature of the cuelib parser. This 
behaviour
is not something that we want to change, as cue sheets "in the wild" often don't
conform strictly to the standard.

Original comment by [email protected] on 11 May 2008 at 8:18

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant