Hi, Neil Jerram <[EMAIL PROTECTED]> writes:
> Sorry to have been carrying on this discussion for so long, and for > changing direction a couple of times. If anyone is still reading, I'd > appreciate hearing your thoughts (again). Just a quick note to say: 0. I'm still reading. ;-) 1. Your `init.d' approach looks very promising and simpler than the one before, which is good. 2. I'd let the files in the `init.d' directory do a `(require-load-path-directory ...)' rather than just containing the directory name. A good reason for this is that it is anyway very easy to evaluate those files in a confined environment (e.g. `null-environment' + the `require-load-path-directory' binding). 3. I'm a bit concerned that this approach is not scalable: opening, reading, and evaluating say a dozen of files each time Guile is started may have a noticeable impact on startup time. Maybe those could be loaded lazily, for instance in `try-module-autoload', the first time `%search-load-path' fails. Thanks, Ludovic. _______________________________________________ Guile-user mailing list Guile-user@gnu.org http://lists.gnu.org/mailman/listinfo/guile-user
