How thury/nexocompiler works
nexocompiler is currently a command-line Ajolote lexical analyzer, not a full compiler pipeline. The user supplies a source file (or uses the default example); the CLI reads it, tokenizes its text with a table-driven finite-state automaton, and prints tokens or reports a lexical/file error. The README documents the token categories and matrix-driven recognition. Some helper implementations were omitted from the excerpts, so their internal wiring is not expanded beyond calls visible in the sampled code.
Main entry points: analizador_lexico.py CLI entry · ejemplo.nexo Ajolote source
Components 11
Other components
- User
- Ajolote source
ejemplo.nexo - CLI entry
analizador_lexico.py - File reader
analizador_lexico.py - Tokenizer
analizador_lexico.py - Character classifier
analizador_lexico.py - DFA matrix and delta
analizador_lexico.py - Token type mapping
analizador_lexico.py - Token stream
- Token output
- Error output
Connections 11
- User → CLI entry: runs with file
- Ajolote source → File reader: read text
- CLI entry → File reader: reads file
- File reader → CLI entry: returns text
- CLI entry → Tokenizer: tokenizes text
- Tokenizer → Character classifier: classifies characters
- Tokenizer → DFA matrix and delta: gets transitions
- Tokenizer → Token type mapping: maps acceptors
- Tokenizer → Token stream: produces tokens
- CLI entry → Token output: prints tokens
- CLI entry → Error output: reports errors