Go to file

Motiejus Jakštys f5f54fcbe8 parser: propagate errors via setjmp/longjmp instead of exit(1)

Replace 32 parse-error exit(1) calls with longjmp to allow callers to
detect and handle parse failures. The OOM exit(1) in
astNodeListEnsureCapacity is kept as-is.

Add has_error flag to Ast, wrap parseRoot() with setjmp in astParse(),
and update test infrastructure to use the C parser for testError tests.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-02-11 14:40:31 +00:00

.clang-format

fmt

2025-01-08 19:04:40 +01:00

.gitignore

zig 0.15.1

2026-02-10 10:03:44 +00:00

AGENTS.md

zig build -Dcc=tcc

2026-02-10 10:47:27 +00:00

ast.c

parser: propagate errors via setjmp/longjmp instead of exit(1)

2026-02-11 14:40:31 +00:00

ast.h

parser: propagate errors via setjmp/longjmp instead of exit(1)

2026-02-11 14:40:31 +00:00

build.zig

parser: implement for loops, port for/while loop test

2026-02-11 14:40:18 +00:00

check_test_order.py

parser: reorder tests, fix check_test_order.py for new file layout

2026-02-11 14:40:30 +00:00

common.h

fix tcc

2026-02-10 11:35:41 +00:00

LICENSE

update license

2026-02-11 14:40:02 +00:00

main.c

fix tcc

2026-02-10 11:35:41 +00:00

parser_test.zig

parser: propagate errors via setjmp/longjmp instead of exit(1)

2026-02-11 14:40:31 +00:00

parser.c

parser: propagate errors via setjmp/longjmp instead of exit(1)

2026-02-11 14:40:31 +00:00

parser.h

parser: propagate errors via setjmp/longjmp instead of exit(1)

2026-02-11 14:40:31 +00:00

README.md

reorder tests better

2026-02-11 14:40:26 +00:00

test_all.zig

start with parser tests

2025-01-04 22:47:51 +01:00

tokenizer_test.zig

zig 0.15.1

2026-02-10 10:03:44 +00:00

tokenizer.c

fix tcc

2026-02-10 11:35:41 +00:00

tokenizer.h

more parser

2025-01-01 17:26:58 +02:00

zig0.c

fix tcc

2026-02-10 11:35:41 +00:00

zig-interp.txt

add some notes

2025-07-01 19:48:18 +00:00

README.md

zig0 aspires to be an interpreter of zig 0.15.1 written in C.

Testing

Quick test:

zig build fmt && zig build

Debugging tips

Test runs infinitely? Build the test program executable:

$ zig build test -Dno-exec

And then run it, capturing the stack trace:

gdb -batch
-ex "python import threading; threading.Timer(1.0, lambda: gdb.post_event(lambda: gdb.execute('interrupt'))).start()"
-ex run
-ex "bt full"
-ex quit
zig-out/bin/test

You are welcome to replace -ex "bt full" with anything other of interest.