Path: csiph.com!weretis.net!feeder6.news.weretis.net!news.misty.com!news.iecc.com!.POSTED.news.iecc.com!nerds-end From: Hans-Peter Diettrich Newsgroups: comp.compilers Subject: Re: Graphical representations of syntax trees? Date: Sun, 6 Feb 2022 23:38:31 +0100 Organization: Compilers Central Lines: 21 Sender: news@iecc.com Approved: comp.compilers@iecc.com Message-ID: <22-02-007@comp.compilers> References: <22-02-004@comp.compilers> <22-02-005@comp.compilers> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit 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 X-submission-address: compilers@iecc.com X-moderator-address: compilers-request@iecc.com X-FAQ-and-archives: http://compilers.iecc.com Xref: csiph.com comp.compilers:2886 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