head     1.1;
branch   1.1.1;
access   ;
symbols  start:1.1.1.1 project:1.1.1;
locks    ; strict;
comment  @# @;


1.1
date     2009.07.09.02.51.46;  author yo2dh;  state Exp;
branches 1.1.1.1;
next     ;

1.1.1.1
date     2009.07.09.02.51.46;  author yo2dh;  state Exp;
branches ;
next     ;


desc
@@



1.1
log
@Initial revision
@
text
@
  Ideally, the entire thing should be do-able as a post-pass over
  the generated tree; I'm thinking of doing a couple simple examples
  of this to function as extra documentation.  Some of the possible
  things I was considering:
    1) Call-graph generator
    2) Included file analysis (was the include necessary, etc.)
    3) Struct-packing analysis (is there excessive packing waste
                                for struct component alignment)

@


1.1.1.1
log
@CVS TEST
@
text
@@
