How devrodofc/analisador-lexico works
This is a small educational Java compiler front end. Its documented workflow reads input.txt, creates a generated JFlex scanner, and starts the generated CUP parser, which pulls tokens and performs parsing with simple semantic actions for declarations, assignments, conditionals, loops, and arithmetic expressions. The graph focuses on runtime behavior; generator specifications are omitted. Relationships are limited to the excerpts and README, so grammar details beyond the shown parser actions are not expanded.
Main entry points: Main.java Compiler entry · parser.java Syntax and actions · Lexer.java Lexical scanner · sym.java Token symbols
Components 7
Runtime entry
- Compiler entry
src/Main.java - Source input
input.txt
Front-end analysis
- Lexical scanner
gen/lexer/Lexer.java - Syntax and actions
gen/parser/parser.java
Token contract
- Token symbols
gen/parser/sym.java
Other components
- User
- Console output
Connections 9
- User → Compiler entry: runs
README.md - Compiler entry → Source input: reads
src/Main.java - Compiler entry → Lexical scanner: creates
src/Main.java - Compiler entry → Syntax and actions: starts
src/Main.java - Syntax and actions → Lexical scanner: pulls tokens
gen/parser/parser.java - Lexical scanner → Token symbols: uses tokens
gen/lexer/Lexer.java - Syntax and actions → Token symbols: defines symbols
gen/parser/parser.java - Syntax and actions → Console output: prints actions
gen/parser/parser.java - Compiler entry → Console output: prints status
src/Main.java