anaru03/cps-analyzer

Purpose and entry points

Cps-analyzer is a Java 17 compiler-front-end exercise for Compiscript: it performs lexical and syntactic analysis, reports structured errors, and exposes both CLI and HTTP-facing entry points. Maven builds the project and invokes ANTLR 4 code generation from src/main/antlr4/gt/edu/uvg/compiscript/Compiscript.g4.

Primary launch classes are src/main/java/gt/edu/uvg/compiscript/CompiscriptApplication.java for the application/API runtime and src/main/java/gt/edu/uvg/compiscript/cli/Main.java for file-oriented command-line analysis.

Language definition and generated parser boundary

The Compiscript grammar is the authoritative language contract: src/main/antlr4/gt/edu/uvg/compiscript/Compiscript.g4. ANTLR-generated lexer/parser artifacts are an implementation boundary between grammar specification and handwritten analysis adapters.

A duplicate top-level grammar, Gramática de Compiscript.g4, and language definition document, Definición de Compiscript.md, provide source/reference context, but the Maven-standard grammar path is the likely build input.

Lexical analysis stage

src/main/java/gt/edu/uvg/compiscript/lexer/AnalizadorLexico.java wraps the ANTLR lexer into a domain API. It consumes source text and produces recognized-token and lexical-error results through ResultadoLexico.java and TokenReconocido.java.

ANTLR failures are captured rather than leaked directly through EscuchadorErroresLexicos.java and represented as ErrorLexico.java. This isolates parser/API/CLI callers from ANTLR listener types and provides a stable diagnostic model.

Syntactic analysis stage

src/main/java/gt/edu/uvg/compiscript/parser/AnalizadorSintactico.java drives parsing over the token stream produced from Compiscript input. It returns ResultadoSintactico.java and captures parser diagnostics as ErrorSintactico.java.

EscuchadorErroresSintacticos.java and EstrategiaErroresSintacticos.java define the parser error-handling boundary: custom listening and recovery behavior can collect multiple useful errors rather than relying on default ANTLR console output or fail-fast semantics.

Analysis orchestration and HTTP boundary

src/main/java/gt/edu/uvg/compiscript/api/AnalisisService.java is the application-level coordinator: it should sequence lexical and syntactic analysis and consolidate outcomes. src/main/java/gt/edu/uvg/compiscript/api/AnalisisController.java adapts that capability to an HTTP API.

The API contract is isolated in DTOs: request input in dto/SolicitudAnalisis.java, aggregate response in dto/RespuestaAnalisis.java, and externally serializable diagnostics in dto/ErrorAnalisis.java. This keeps transport payloads independent of lexer/parser domain classes.

Input/output flow

Source reaches the system either as a .cps file through cli/Main.java or as request content through api/AnalisisController.java. Both routes converge on analysis logic, then pass through lexer tokenization and parser validation. Results return recognized tokens and/or diagnostics, with error location/category information translated into domain or API DTOs.

Example inputs establish expected success and failure modes: ejemplos/archivo_correcto.cps, ejemplos/error_lexico1.cps, and ejemplos/error_parser1.cps.

Runtime and infrastructure

The backend runtime is Java 17 with Maven and ANTLR 4, configured by pom.xml. The presence of CompiscriptApplication.java, controller, and service indicates a Spring-style HTTP application layer.

A separate Vite/Vue frontend exists under frontend/src/App.vue and frontend/src/main.js. Its integration contract is the backend analysis API, though no deployment or proxy configuration is evident from the supplied tree.