With standard gerbil new project structure, how to gerbil interactive hello/main.ss?

[metaleap]

Newb question time! With the gerbil new hello-world starter project that does successfully gerbil build — I'm trying to work out an interpreted gerbil run equivalent, but both gerbil interactive hello/main.ss and cd hello && gerbil interactive main.ss error out with:

*** ERROR IN gx#core-resolve-library-relative-module-path -- 
*** ERROR IN "hello/main.ss"@5.9-5.14
--- Syntax Error: Cannot resolve relative module path; not in module context
... form:   ./lib

Does the interpreter not support/grok all that the compiler (or build script) does, out of box? Namely here the import of relative dir path ./lib? (Manually also specifying it via -L arg btw doesn't seem make a difference wrt the above error.)

[vyzo]

You can try gerbil env bash to get a subshell with the right GERBIL_PATH.

You should then be able to use the interpreter normally, with your compiled modules visible.

Pethaps we can add a a gerbil pkg run command to simplify this, and alias it to gerbil run as well.

[metaleap]

Pethaps we can add a a gerbil pkg run command to simplify this, and alias it to gerbil run as well.

I think that'd be desirable, it's such a widespread pattern out there by now, well at least from the go run / dotnet run / npm run etc. vantage

[vyzo]

Ah, actually there is an old limitation in the interpreter not understanding relative paths.

We should fix this.

[vyzo]

Aha, the plot thickens; the limitation i was thinking of is no longer there, but there is another bug at play:

Here is what the canonical way to run main interpreted would be:

$ gerbil new -n test
$ gerbil env gxi  test/main.ss

which fails:

$ gerbil env gxi test/main.ss 
*** ERROR IN gx#core-resolve-library-relative-module-path -- 
*** ERROR IN "test/main.ss"@5.9-5.14
--- Syntax Error at (expand top): cannot resolve relative module path; not in module context
... form:   ./lib
*** ERROR IN std/misc/process#run-process__% -- 
*** ERROR IN "misc/process.ss"@28.35-28.46 [ProcessError]: process exited with non-zero status
--- irritants: "gxi" 17920 (path: "gxi" arguments: ("test/main.ss") environment: #f directory: #f stdin-redirection: #f stdout-redirection: #f stderr-redirection: #f pseudo-terminal: #f show-console: #f) 
--- continuation backtrace:
[0] raise                                                                              
[1] std/misc/process#run-process__%                                                                                                                                            ((if (procedure? _%check-status258971%_) _%check-status258971%_ std/misc/proc...

The issue here is that gxi evals this as a script, and there is no module context to anchor the resolution of the module path, so it fails.

This is a bug.

[vyzo]

Opened issue for tracking resolution: #1242