unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: <dsmich@roadrunner.com>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel@gnu.org
Subject: Re: guile-vm .go files in GUILE_LOAD_PATH
Date: Thu, 18 Sep 2008 16:49:45 -0400	[thread overview]
Message-ID: <18730150.2888471221770986002.JavaMail.root@cdptpa-web08-z02> (raw)

---- Andy Wingo <wingo@pobox.com> wrote: 
> Hi,
> 
> On Thu 18 Sep 2008 00:57, <dsmich@roadrunner.com> writes:
> 
> > Basically, a .go file will be preferred over a .scm file even if the
> > .scm file is earlier in the load-path. I think that the file earlier
> > in the load-path should win.
> 
> A few thoughts:
> 
>  (1) Guile shouldn't have installed paths (its system paths) in its path
>      when running uninstalled, otherwise you can get strange issues like
>      you saw -- it's not limited to .go files, it could be .scm as well

True.

>  (2) I can imagine cases in which you would want compiled files not in
>      the same location as source; e.g. /usr/lib64/guile/ vs
>      /usr/share/guile/; although currently .go files are not
>      platform-dependent (I don't think)

Hmm.  Also true.

>  (4) We already check to make sure that the .go file is newer than the
>      .scm file

Good.

> I would suggest that the current way is sufficient, if we disable
> loading from the installed paths when running pre-inst-guile; because I
> kinda want to allow (2), but I don't want to deal with ordering issues
> within %load-path of "compiled locations" versus "source locations".

I'm pretty sure the case of not using the already installed system .scm files while building is handled now.  I'm thinking more along the lines of some user wanted to override a system file for some reason. This issue came up for me when I wanted to use a newer gnus than what came with the system supplied emacs.  At that time I didn't have admin privs so I just installed gnus somewhere under my home dir and made sure that the emacs load path searched there first.  Can this situation ever come up in Guile?  Maybe.

As Neil mentioned, emacs is a good example to follow.  That's why I'm suggesting this.

> Sorry about your bug, I know it was a bit painful. But you would not
> have had it if guile were operating correctly in the first place,
> regardless of the .go vs .scm issue.

No problem there.  Finding (and fixing) bugs is what makes using developing code fun. ;^)

Thanks,
   -Dale





             reply	other threads:[~2008-09-18 20:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-18 20:49 dsmich [this message]
2008-09-18 21:14 ` guile-vm .go files in GUILE_LOAD_PATH Andy Wingo
2008-09-18 22:32 ` Ludovic Courtès
  -- strict thread matches above, loose matches on Subject: below --
2008-09-17 22:57 dsmich
2008-09-18  3:55 ` David Séverin
2008-09-18  7:26 ` Neil Jerram
2008-09-18 18:40 ` 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=18730150.2888471221770986002.JavaMail.root@cdptpa-web08-z02 \
    --to=dsmich@roadrunner.com \
    --cc=guile-devel@gnu.org \
    --cc=wingo@pobox.com \
    /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).