1. file analyzer
- Posted by bytebrain <bytebrain at MINDSPRING.COM>
Aug 11, 1999
-
Last edited Aug 12, 1999
-------Phoenix-Boundary-07081998-
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: Quoted-printable
Hi guys,
I've just returned to Euphoria after a
long hiatus, and decided to try a file analyzer
of sorts as my first project. If you are
interested in something like that, read on.
I have submitted a first swing at it to Robert,
so it should be showing up on the contributions
page sometime soon. I would appreciate any
comments you have as to the potential usefulness
of such a thing.
The one I sent to RDS will (theoretically) churn
out the following info about a given source file:
LOCALS: variables, constants, functions, procedures
and types
GLOBALS: ditto
EXTERNALS: variables/constants not defined in the
target file, routines likewise.
INCLUDES: files included via 'include' statements
*It also shows the arguments and private variables
for each routine (except the external routines, of
course)
More information is available in the readme.txt
included with the archive.
It just occurred to me that I never did get around
to testing it on any machine slower than a 366 Mhz,
so if you are using a slower machine you might want
to try it on a small source code file first to make
sure it's not going to just sit there all day/night.
Craig
bytebrain at mindspring.com
----------------------------------------------------
There are two ways to do great mathematics. The first
way is to be smarter than everybody else. The second
way is to be stupider than everybody else -- but
persistent. (Raoul Bott)
-------Phoenix-Boundary-07081998---
