diff options
author | 2003-08-02 20:46:00 -0700 | |
---|---|---|
committer | 2005-04-07 21:01:01 -0700 | |
commit | f02b6adcd05720e8655b8b0fd64f81791e63f987 (patch) | |
tree | 11ef0426ec456395fb3af93ffc8166deb10d84f9 /README | |
parent | Update copyright notices to reflect the fact that Transmeta (diff) | |
download | sparse-f02b6adcd05720e8655b8b0fd64f81791e63f987.tar.gz sparse-f02b6adcd05720e8655b8b0fd64f81791e63f987.tar.bz2 sparse-f02b6adcd05720e8655b8b0fd64f81791e63f987.zip |
Add a note in the readme about the fact that we now do a five-
phase parse: the last phase is the inline function expansion
and the tree simplification.
Diffstat (limited to 'README')
-rw-r--r-- | README | 3 |
1 files changed, 2 insertions, 1 deletions
@@ -26,13 +26,14 @@ And no, it doesn't use lex and yacc (or flex and bison). In my personal opinion, the result of using lex/yacc tends to end up just having to fight the assumptions the tools make. -The parsing is done in four phases: +The parsing is done in five phases: - full-file tokenization - pre-processing (which can cause another tokenization phase of another file) - semantic parsing. - lazy type evaluation + - inline function expansion and tree simplification Note the "full file" part. Partly for efficiency, but mostly for ease of use, there are no "partial results". The library completely parses one |