Re: Algorithm for Structurizing

tleylan@aloha.com
Sun, 11 Dec 1994 09:53:07 GMT

          From comp.compilers
Related articles
Algorithm for Structurizing jlapp@nova.umd.edu (1994-12-04)
Re: Algorithm for Structurizing donawa@bnr.ca (chris (c.d.) donawa) (1994-12-09)
Re: Algorithm for Structurizing kik@zia.cray.com (1994-12-05)
Re: Algorithm for Structurizing danhicks@aol.com (1994-12-06)
Re: Algorithm for Structurizing tleylan@aloha.com (1994-12-07)
Re: Algorithm for Structurizing tleylan@aloha.com (1994-12-11)
Re: Algorithm for Structurizing tleylan@aloha.com (1994-12-13)
Re: Algorithm for Structurizing tleylan@aloha.com (1994-12-14)
| List of all articles for this month |
Newsgroups: comp.compilers,comp.lang.c,comp.programming
From: tleylan@aloha.com
Keywords: analysis, comment
Organization: Flex Information Network HAWAII
References: <9412102334.AA21441@bcrks282.bnr.ca>
Date: Sun, 11 Dec 1994 09:53:07 GMT

On Sat, 10 Dec 1994, chris (c.d.) donawa wrote:


> See ftp://acaps.cs.mcgill.ca/ftp/ftp.html and Ana Erosa's technical
> memo. She implemented an automatic restructurer for our McCAT C
> compiler.


I'll go get it but perhaps I'm confusing "restructurer". Is it a tech
term because unless you mean "pretty printer" I can't see how an external
program can determine that (for instance):


  for x = 1 to 10
      thisfunction()


  for y = 1 to 10
        thatfunction()


could be expressed as


  for z = 1 to 10
        thisfunction()
        thatfunction()


(no particular language represented here BTW) without knowledge about
what the function calls do.


tom
[Restructurers typically attempt to turn goto spaghetti into for and while
loops. -John]
--

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.