pascal 0.1.7

A modern Pascal compiler with build/intepreter/package manager built with Rust
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102

# Development Guide

## Profiling

CPU profiling is available when building with the `profile` feature:

```bash
cargo build --features profile
```

Run a program with profiling to generate a flamegraph:

```bash
pascal run myprog.pas --profile
# Writes flamegraph.svg by default

pascal run myprog.pas --profile --profile-output cpu.svg
```

Open the generated SVG in a browser to view the flamegraph. The graph shows where the interpreter spends time during execution.

## Language Server (LSP)

Build with the `lsp` feature and start the server on stdio:

```bash
cargo build --features lsp
pascal lsp
```

Configure your editor to use `pascal lsp` as the Pascal language server. The server provides:

- **Completion** — keywords, variables, types, procedures, functions, builtins
- **Hover** — symbol documentation
- **Diagnostics** — parse errors on open/change

VS Code / Cursor: install the grammar from `editors/vscode/` or point `files.associations` at the TextMate grammar in `syntaxes/`.

## REPL

Interactive Pascal session:

```bash
pascal repl
```

Commands: `:help`, `:quit`, `:clear`, `:history`, `:complete <prefix>`.

## Memory Leak Check

Analyze interpreter scopes after a run:

```bash
pascal leak-check program.pas
pascal leak-check program.pas --strict   # exit 1 if heap objects remain
pascal run program.pas --leak-check
```

Reports arrays, objects, and records still held in interpreter scopes at program end.

## Memory Leak Detection (Sanitizers)

For compiled Pascal binaries and the interpreter:

### AddressSanitizer (Linux/macOS)

Build and run with AddressSanitizer to detect memory leaks and buffer overflows:

```bash
RUSTFLAGS="-Z sanitizer=address" cargo build --target x86_64-unknown-linux-gnu
# Or on macOS (aarch64):
RUSTFLAGS="-Z sanitizer=address" cargo build --target aarch64-apple-darwin
```

Then run your tests or interpreter:

```bash
cargo test
pascal run program.pas
```

### Valgrind (Linux)

If you have a compiled Pascal binary (from another backend), run:

```bash
valgrind --leak-check=full ./my_program
```

For the interpreter itself:

```bash
valgrind --leak-check=full cargo run -- run program.pas
```

### Running Tests with Sanitizers

```bash
RUSTFLAGS="-Z sanitizer=address" cargo test
```

Note: Sanitizers require a compatible target. On macOS, `x86_64-apple-darwin` and `aarch64-apple-darwin` are supported for AddressSanitizer.