Re: [PATCH] `try-module-autoload' and `current-reader'

[EMAIL PROTECTED] (Ludovic Courtès) writes: > Hi, > > Neil Jerram <[EMAIL PROTECTED]> writes: > >> But that would still bring in a start-stack and so change backtraces, >> so I'd prefer not. > > Oh, right. > >> I really think with-fluids is the way to go. If you agree, I'll make >> this change in

Re: [PATCH] `try-module-autoload' and `current-reader'

Hi, Neil Jerram <[EMAIL PROTECTED]> writes: > But that would still bring in a start-stack and so change backtraces, > so I'd prefer not. Oh, right. > I really think with-fluids is the way to go. If you agree, I'll make > this change in CVS. Ok, let's go for it! ;-) Thanks, Ludovic. __

Re: [PATCH] `try-module-autoload' and `current-reader'

[EMAIL PROTECTED] (Ludovic Courtès) writes: > But still, shouldn't we use `load' (not `load-module', because of the > path concern) to load modules? If so, the patch would just substitute > `load' to `primitive-load'. But that would still bring in a start-stack and so change backtraces, so I'd p

Re: [PATCH] `try-module-autoload' and `current-reader'

Hi, Neil Jerram <[EMAIL PROTECTED]> writes: > process-use-modules -> resolve-interface -> resolve-module -> > try-load-module -> try-module-autoload > > (Arguably try-module-autoload could be better named.) Sorry, I had missed that point. >> Also, the `with-fluids' framing is already provided b

Re: [PATCH] `try-module-autoload' and `current-reader'

[EMAIL PROTECTED] (Ludovic Courtès) writes: > Hi, > > Neil Jerram <[EMAIL PROTECTED]> writes: > >> 1. Starting a new stack (the start-stack form in R4RS's load). This >>affects backtraces, and it is occasionally useful for a backtrace >>to show that module X is being loaded because of cod

Re: [PATCH] `try-module-autoload' and `current-reader'

Kevin Ryde <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED] (Ludovic Courtès) writes: >> >> Can you explain that? > > See load-module in boot-9.scm, hairy stuff. And if called from try-module-autoload, I believe this hairy stuff would come into play if %load-path included relative directories (suc

Re: [PATCH] `try-module-autoload' and `current-reader'

[EMAIL PROTECTED] (Ludovic Courtès) writes: > > Can you explain that? See load-module in boot-9.scm, hairy stuff. ___ Guile-devel mailing list Guile-devel@gnu.org http://lists.gnu.org/mailman/listinfo/guile-devel

Re: [PATCH] `try-module-autoload' and `current-reader'

Hi, Kevin Ryde <[EMAIL PROTECTED]> writes: > I've been meaning to add something to the docs on how load is relative > to the current file (unless you use "./"). Can you explain that? Thanks, Ludovic. ___ Guile-devel mailing list Guile-devel@gnu.org

Re: [PATCH] `try-module-autoload' and `current-reader'

Neil Jerram <[EMAIL PROTECTED]> writes: > >it is occasionally useful for a backtrace to show that module X >is being loaded because of code from module Y. Yes, I've wrestled with that on some inadvertently circular autoloads. I ended up using %load-hook to show what was actually happening

Re: [PATCH] `try-module-autoload' and `current-reader'

Hi, Neil Jerram <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED] (Ludovic Courtès) writes: > >> Hi, >> >> In `boot-9.scm', `try-module-autoload' should be using `load-module', >> and not `primitive-load', when loading a non-compiled module. The >> reasons are (i) non-autoloaded modules are loaded

Re: [PATCH] `try-module-autoload' and `current-reader'

[EMAIL PROTECTED] (Ludovic Courtès) writes: > Hi, > > In `boot-9.scm', `try-module-autoload' should be using `load-module', > and not `primitive-load', when loading a non-compiled module. The > reasons are (i) non-autoloaded modules are loaded using `load-module' > and (ii) `load-module' and `pri

[PATCH] `try-module-autoload' and `current-reader'

Hi, In `boot-9.scm', `try-module-autoload' should be using `load-module', and not `primitive-load', when loading a non-compiled module. The reasons are (i) non-autoloaded modules are loaded using `load-module' and (ii) `load-module' and `primitive-load' interact differently with the `current-read