|Syntax directed program editing firstname.lastname@example.org (1992-02-05)|
|Re: Syntax directed program editing email@example.com (1992-02-06)|
|Re: Syntax directed program editing firstname.lastname@example.org (1992-02-15)|
|Re: Syntax directed program editing nickh@CS.CMU.EDU (1992-02-07)|
|Re: Syntax directed program editing email@example.com (1992-02-07)|
|Re: Syntax directed program editing firstname.lastname@example.org (1992-02-07)|
|Re: Syntax directed program editing email@example.com (1992-02-11)|
|From:||firstname.lastname@example.org (Dr A. N. Walker)|
|Organization:||Maths Dept., Nott'm Univ., UK.|
|Date:||Fri, 7 Feb 1992 17:58:38 GMT|
In article 92-02-024 email@example.com (Richard
>Why aren't there more editors which operate directly on the parse trees of
>languages? Are there fundamental problems with this approach?
Yes. Actually, despite the moderator's comments, it works
reasonably well for some languages, like Pascal, for which the textual
form of the program is verbose, so that it's worth spending some time to
economise on keystrokes; it's hopeless for terse languages like C.
The first problem with *any* syntax-directed editing is that the
user needs to understand the syntax of the language being written. This
is not as common as it ought to be, especially for the beginners who
might, in principle, benefit most from a helpful editor.
The second problem is that the syntax that a compiler would like
to use [and that is usually the syntax by which the language is defined]
is different from the syntax that a helpful syntax-directed editor should
use. Example: the compiler would probably like to treat all standard
functions and procedures in the same general way as user-defined ones; we
found it much more helpful if they were presented to the user as special
forms of statement or expression.
Andy Walker, Maths Dept., Nott'm Univ., UK.
[How do you handle changes like moving a statement across an "end" ? -John]
Return to the
Search the comp.compilers archives again.