Update of /project/climacs/cvsroot/papers/ilc2005/syntax In directory common-lisp.net:/tmp/cvs-serv27048

Modified Files: climacssyntax.tex Log Message: tiny extrapolations on current structure

Date: Fri May 20 10:18:33 2005 Author: crhodes

Index: papers/ilc2005/syntax/climacssyntax.tex diff -u papers/ilc2005/syntax/climacssyntax.tex:1.5 papers/ilc2005/syntax/climacssyntax.tex:1.6 --- papers/ilc2005/syntax/climacssyntax.tex:1.5 Wed May 18 15:56:45 2005 +++ papers/ilc2005/syntax/climacssyntax.tex Fri May 20 10:18:33 2005 @@ -102,6 +102,9 @@ 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 @@ 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 @@ 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 @@ 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}