eval and compile procedure not working for min/max library when arity-check is disabled

[leo-ard]

To reproduce (on dev branch):

> gsi -:r4rs rsc.scm -t js -l min -x test tests/00-ribbit/35-eval.scm -o test.js
> /test <<< "(* 6 7)"                                                          
/home/leonard/code/dirowars/ribbit/src/test:157
    let o = pc[1];
              ^

TypeError: Cannot read properties of undefined (reading '1')
    at run (/home/leonard/code/dirowars/ribbit/src/test:157:15)
    at Object.<anonymous> (/home/leonard/code/dirowars/ribbit/src/test:223:3)
    at Module._compile (node:internal/modules/cjs/loader:1254:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1308:10)
    at Module.load (node:internal/modules/cjs/loader:1117:32)
    at Module._load (node:internal/modules/cjs/loader:958:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
    at node:internal/main/run_main_module:23:47

Node.js v18.16.0

This bug is reproducible in py, js and asm hosts.

However, if we activate arity-check, then everything runs fine :

> gsi -:r4rs rsc.scm -t js -l min -f+ arity-check -x test tests/00-ribbit/35-eval.scm -o test.js
> ./test <<< "(* 6 7)"                                                                          
42

This bug is probably due to changes in the calling protocol, and min/max libraries where not updated accordingly. The bug is probably in the min/max library.

[leo-ard]

I changed the tests 35-eval and 50-repl to use r4rs lib instead of min/max because of this bug. See commit : 54a9e93

[leo-ard]

Seems to affect 90-macro as well