Thien-Thi Nguyen <[EMAIL PROTECTED]> writes: > i believe this bug is actually a misunderstanding. i could not > reproduce the above behavior. see below for a more straightforward way > to see if some proc is available. > > thi > > _____________________________ > guile> read-and-eval! > #<primitive-procedure read-and-eval!> > guile> (version) > "1.5.2" > guile> >
Hm. Maybe when I built Guile something got left out? Alex. guile> read-and-eval! <unnamed port>: In expression read-and-eval!: <unnamed port>: Unbound variable: read-and-eval! ABORT: (unbound-variable) Type "(backtrace)" to get more information or "(debug)" to enter the debugger. guile> (backtrace) Backtrace: In unknown file: ?: 0* read-and-eval! Type "(debug-enable 'backtrace)" if you would like a backtrace automatically if an error occurs in the future. guile> (version) "1.7.0" guile> (apropos "read-and-eval") guile> -- http://www.geocities.com/kensanata/ Coffee should be black as hell, strong as death and sweet as love. -- Turkish proverb _______________________________________________ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
