Order of definitions in REPL

[Joe Near]

Definitions that call functions defined later in the file don't seem to be handled as I would expect when loaded at the REPL. When run as a script, they work as I expect. For example:

jnear@sandstone r6mk $ cat test.scm
#!/usr/bin/env scheme-script
(import (rnrs))

(define foo
  (lambda ()
    (bar)))

(define bar
  (lambda ()
    (display "bar!")
    (newline)))

(foo)
jnear@sandstone r6mk $ ikarus --r6rs-script test.scm
bar!
jnear@sandstone r6mk $ ikarus test.scm
Ikarus Scheme version 0.0.3+ (revision 1477, build 2008-05-13)
Copyright (c) 2006-2008 Abdulaziz Ghuloum

Unhandled exception:
 Condition components:
   1. &assertion
   2. &who: eval
   3. &message: "unbound variable"
   4. &irritants: (bar)

[leppie (leppie)]

You can always just start the REPL and call (load "test.scm") (or (include "test.scm")).

[Abdulaziz Ghuloum (aghuloum)]

I noticed this yesterday and was going to report it, but you raced me to it. Thanks.

[leppie (leppie)]

How exactly does it work? It starts the REPL and then do a load/include on the filename(s) passed as parameters? How do you pass additional parameters/files?

[Abdulaziz Ghuloum (aghuloum)]

Fixed in 1478. Let me know if that messed up something else.

[Abdulaziz Ghuloum (aghuloum)]

On May 15, 2008, at 6:37 AM, leppie wrote:
> How exactly does it work? It starts the REPL and then do a load/
> include
> on the filename(s) passed as parameters? How do you pass additional
> parameters/files?

When you start "ikarus file1 file2 file3 ...", the contents of the
files will be evaled one by one before the repl prompt comes up.

[leppie (leppie)]

Thanks :)

So it is effectively:

ikarus
> (include file1)
> (include file2)
> (include file3)
...
> ; this is where we end

?