Skip to content
Snippets Groups Projects
Commit 8f53cd33 authored by Christophe Rhodes's avatar Christophe Rhodes
Browse files

tiny extrapolations on current structure

parent d8e88098
No related branches found
No related tags found
No related merge requests found
......@@ -102,6 +102,9 @@ text is up-to-date at every point during an edit. The per-buffer
approach is appropriate when the parse tree will also be used for some
other display or analysis of the text in the buffer.
Earley parser: discussion of generality and asymptotic efficiency (in
general and for usual cases).
\section{Syntaxes}
We describe two different approaches to syntax analysis in the Climacs
......@@ -127,11 +130,23 @@ grammar.
Christophe might want to describe the Prolog syntax a bit here. In
particular any details having to do with the implementation of
operator precedence as specified in the ISO Prolog standard might be
interesting. [ Maybe just the \textit{priority} stuff? I think that's
interesting.
[ Maybe just the \textit{priority} stuff? I think that's
the only interesting bit of non-context-freeness; user-defined
operators is OK because you can't actually define and use a new
operator in the same directive. ]
Float tokenizer (not interesting, but not yet done)
Need for inheritable grammars / tokenizers: most Prologs deviate from
ISO slightly, mostly in surface syntax rather than in the engine.
Examples: \verb+"ab\x011\"+, \texttt{0'''}, \texttt{[H|T]} when
\texttt{|} is an operator.
Possibility (probably ``Future Work'') to make nice integrated Prolog
environment.
The TTCN3 syntax is implemented with a high-level macro which defines
classes and adds syntax rules using the syntax protocol for each
terminal and non-terminal in the grammar. The syntax of this macro
......@@ -183,6 +198,11 @@ not so easy. Chords, obviously; beams, comments... Should we try to
capture a BNF or something? I suppose it depends how we're doing for
space.
Ornaments are simple to model, as they are merely modifiers to note
objects; higher-level grouping things (beams, connecting lines) have
their own semi-independent identity, despite not being notated as such
in the textual \TabCode.
Need whole-buffer function to present an alternative whole-system view
on the data.
......@@ -190,10 +210,11 @@ Editor is in use for cataloguing European lute music, and supports
research into more advanced notations (for e.g. editorial comment, or
manuscript markup)
Efficiency concerns assuaged by typical locality of edit, incremental
redisplay on the tablature buffer.
Efficiency concerns assuaged by typical locality of edit, CLIM
incremental redisplay on the tablature buffer.
MIDI feedback.
MIDI feedback. At present, based on Apple's extremely badly
documented CoreMIDI framework; a port to alsalib is on the cards.
\section{Conclusion}
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment