4e942b5373
Rename all example tests/companions to the XXXX-category-test-name scheme (per-category 100-blocks: basic 0010, types 0100, ... errors 1000, diagnostics 1100, ffi 1200, ffi-objc 1300, ffi-jni 1400, vectors 1500, platform 1600). Companions and dir/C fixtures move in lockstep with their parent test; #import/#source/#include paths rewritten to match. Expected output now lives in examples/expected/ (a sibling dir of the tests) split into three streams per the new convention: <name>.exit / <name>.stdout / <name>.stderr (+ optional <name>.ir) run_examples.sh rewritten: scans examples/ and issues/ for an expected/<name>.exit marker, captures stdout and stderr separately (no more 2>&1), compares each stream + exit + optional IR snapshot. Behavior validated unchanged: every renamed test reproduces its prior merged output + exit (diffs limited to file paths/basenames embedded in diagnostics + traces, which correctly reflect the new names). Suite: 292 passed, 0 failed. 50-smoke.sx split + issue relocation + docs follow in subsequent commits.
22 lines
682 B
Plaintext
22 lines
682 B
Plaintext
// Phase 2 step 2.16a (PLAN-FFI.md): xfail then green for the
|
|
// `#jni_env(env) { body }` block-form intrinsic.
|
|
//
|
|
// Scopes a JNIEnv* over a lexical block. Step 2.16a lands parser +
|
|
// AST + sema acceptance — the body runs as a normal block, the env
|
|
// arg is captured but not yet used at lowering. The TL push/pop
|
|
// semantics (step 2.16b) and lexical-direct resolution in `#jni_call`
|
|
// (step 2.16c) follow.
|
|
//
|
|
// Today the lexer doesn't recognise `#jni_env` and the parser errors
|
|
// at the unknown directive token.
|
|
|
|
#import "modules/std.sx";
|
|
|
|
main :: () -> s32 {
|
|
synth_env : *void = null;
|
|
#jni_env(synth_env) {
|
|
print("inside #jni_env scope\n");
|
|
}
|
|
0;
|
|
}
|