unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: Build failure on master
Date: Wed, 15 Jul 2009 00:05:34 +0200	[thread overview]
Message-ID: <878wiq539t.fsf@gnu.org> (raw)
In-Reply-To: 87my775mpo.fsf@arudy.ossau.uklinux.net

Neil Jerram <neil@ossau.uklinux.net> writes:

> ludo@gnu.org (Ludovic Courtès) writes:

[...]

>> Eventually, maybe it could handle this gracefully.  For instance, if
>> said object file is from the cache, then it could just recompile and
>> overwrite it with a new object file.
>
> Yes, this is what I'd (intuitively, but without detailed knowledge)
> expect.

I guess this could be achieved by setting up a dynwind/catch block in
`primitive-load-path' when loading things from the cache.  Something to
look at once 1.9.1 is released.

>> Then it could also try to interpret version numbers and determine
>> whether that bytecode is really incompatible, or whether it can
>> interpret it.
>
> Are there scenarios where that would be worthwhile?

Maybe, e.g., when the `.go' version is known to be a strict subset of
the current objcode version.

Thanks,
Ludo'.





  reply	other threads:[~2009-07-14 22:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-12 15:21 Build failure on master Mike Gran
2009-07-12 21:56 ` Ludovic Courtès
2009-07-14  7:26   ` Neil Jerram
2009-07-14 13:19     ` Ludovic Courtès
2009-07-14 13:21     ` Ludovic Courtès
2009-07-14 15:05       ` Neil Jerram
2009-07-14 22:05         ` Ludovic Courtès [this message]
2009-07-23 21:46           ` Andy Wingo
2009-07-23 21:44 ` Andy Wingo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878wiq539t.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).