Re: Pointers to "why C behaves like that ?"

"Roman Shaposhnick" <vugluskr@unicorn.math.spbu.ru>
26 Nov 2002 22:17:19 -0500

          From comp.compilers

Related articles
[42 earlier articles]
Re: Pointers to "why C behaves like that ?" Nicola.Musatti@ObjectWay.it (Nicola Musatti) (2002-11-26)
Re: Pointers to "why C behaves like that ?" nmm1@cus.cam.ac.uk (Nick Maclaren) (2002-11-26)
Re: Pointers to "why C behaves like that ?" peter_flass@yahoo.com (Peter Flass) (2002-11-26)
Re: Pointers to "why C behaves like that ?" fjh@students.cs.mu.OZ.AU (Fergus Henderson) (2002-11-26)
Re: Pointers to "why C behaves like that ?" daniel_yokomiso@softhome.net (Daniel Yokomiso) (2002-11-26)
Re: Pointers to "why C behaves like that ?" thp@cs.ucr.edu (2002-11-26)
Re: Pointers to "why C behaves like that ?" vugluskr@unicorn.math.spbu.ru (Roman Shaposhnick) (2002-11-26)
Re: Pointers to "why C behaves like that ?" vugluskr@unicorn.math.spbu.ru (Roman Shaposhnick) (2002-11-26)
Re: Pointers to "why C behaves like that ?" vugluskr@unicorn.math.spbu.ru (Roman Shaposhnick) (2002-11-26)
Re: Pointers to "why C behaves like that ?" whopkins@alpha2.csd.uwm.edu (Mark) (2002-12-01)
Re: Pointers to "why C behaves like that ?" nmm1@cus.cam.ac.uk (Nick Maclaren) (2002-12-01)
Re: Pointers to "why C behaves like that ?" joachim_d@gmx.de (Joachim Durchholz) (2002-12-01)
Re: Pointers to "why C behaves like that ?" peter_flass@yahoo.com (Peter Flass) (2002-12-01)
[18 later articles]
| List of all articles for this month |
From: "Roman Shaposhnick" <vugluskr@unicorn.math.spbu.ru>
Newsgroups: comp.compilers
Date: 26 Nov 2002 22:17:19 -0500
Organization: St.Petersburg University
References: 02-11-059 02-11-083 02-11-100 02-11-109 02-11-135 02-11-142
Keywords: types, design
Posted-Date: 26 Nov 2002 22:17:19 EST

On 24 Nov 2002 18:33:29 -0500, thp@cs.ucr.edu wrote:
>Dr A. N. Walker <anw@merlot.uucp> wrote:
>+ Charles Bryant <r368714668.ch@chch.demon.co.uk> wrote:
>+><thp@cs.ucr.edu> wrote:
>It should be possible, once a program has been parsed into an abstract
>syntax tree, to present various annotated views of that database,
>regardless of how the original programmer specified the program:
> - adding Hungarian prefixes,
> - adding types etc for implicitly declared variables,
> - displaying keywords in distinctive colors or fonts,
> - adding helpful comments, e.g., "increment(/*changes*/ n)"
> - and so forth.
>I assume that some static analysis tools might already provide
>such services. If so, then some of the arguments against implicity
>typing evaporate.


  It seems that having a way to ask compiler for an AST would benefit
  a lot of people, trying to do something like you've mentioned. The
  question, however is -- where can one get such a tool for languages
  like C and C++.


  Once I had this idea of writing gcc backend that will just emit AST
  in some form, but, unfortunately GCC presents backend with a quite
  distilled version of the AST so to speak, so there is a lot of information
  ( especially for C++ ) lost.


  Have any of you heard of a free tool that can do it ?


Thanks,
Roman.


Post a followup to this message

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