You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 31, 2024. It is now read-only.
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
The text was updated successfully, but these errors were encountered:
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 issue reported on code.google.com by
[email protected]
on 11 May 2008 at 8:12The text was updated successfully, but these errors were encountered: