Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| Graphical representations of syntax trees? johann@myrkraverk.com (Johann 'Myrkraverk' Oskarsson) (2022-02-04) |
| Re: Graphical representations of syntax trees? gah4@u.washington.edu (gah4) (2022-02-06) |
| Re: Graphical representations of syntax trees? anton@mips.complang.tuwien.ac.at (2022-02-06) |
| Re: Graphical representations of syntax trees? DrDiettrich1@netscape.net (Hans-Peter Diettrich) (2022-02-06) |
| Re: Graphical representations of syntax trees? johann@myrkraverk.com (Johann 'Myrkraverk' Oskarsson) (2022-02-07) |
| Re: Graphical representations of syntax trees? anton@mips.complang.tuwien.ac.at (2022-02-07) |
| Re: Graphical representations of syntax trees? christopher.f.clark@compiler-resources.com (Christopher F Clark) (2022-02-07) |
| Re: Graphical representations of syntax trees? alexfrunews@gmail.com (Alexei A. Frounze) (2022-02-07) |
| Re: Graphical representations of syntax trees? stephenjohnlimb@gmail.com (Steve Limb) (2022-02-08) |
| Re: Graphical representations of syntax trees? jonathan@gold.bkis-orchard.net (Jonathan Thornburg) (2022-02-08) |
| [1 later articles] |
| From: | Hans-Peter Diettrich <DrDiettrich1@netscape.net> |
| Newsgroups: | comp.compilers |
| Date: | Sun, 6 Feb 2022 23:38:31 +0100 |
| Organization: | Compilers Central |
| References: | 22-02-004 22-02-005 |
| Injection-Info: | gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="90235"; mail-complaints-to="abuse@iecc.com" |
| Keywords: | parse, tools |
| Posted-Date: | 06 Feb 2022 18:23:06 EST |
On 2/6/22 10:07 PM, gah4 wrote:
> The main complication with doing this, is positioning the items
> on the page.
Right, that's a big problem. For my decompilers I wrote a flexible tree
representation of the parse tree with online navigation through the
tree. Source code for Atari ST in GfA Basic has gone long ago :-(
> I do remember knowing about programs to print out flow charts,
> but that is different. But it also has the same problem of positioning
> on the page.
That's not really different. A parse tree only includes more information
(nodes) than the original flow chart of the code.
Another solution may be a structure like used with source code. Blocks
or functions are not arranged LTR but top down. Subtrees are indented
and broken into multiple lines instead of nodes appended LTR.
DoDi
Return to the
comp.compilers page.
Search the
comp.compilers archives again.