This is the mail archive of the guile@cygnus.com mailing list for the guile project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
"Perry E. Metzger" <perry@piermont.com> writes:
> No one rational is going to use guile if they need to run the "guile
> daemon" at all times to get remotely good performance. We should just
> fix the performance. It is certainly doable.
Along these lines, I have thought that a fruitful way of improving
guile's startup performance would be to first build a basic guile, and
then that guile could invoke the hobbit compiler to compile the guile
init files.
Then the basic guile would be linked with these transformed (into '.o'
files) init file to form the guile executable. This executable would
not read any init files on startup, so it would be fast.
All of this would happen at build time out of the base guile package.
Of course this is just a simple matter of programming ;^)
A similar architecture would work with unexec, but it would probably
be less friendly when attempting to build a special application that
includes all of guile, including the init files.
-russ
--
"There are only two industries that refer to their customers
as 'users'."
-- Edward Tufte