GNU bug report logs - #20968
25.0.50; Be able to specify the output directory for `byte-compile-file'

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: rgm <at> gnu.org, 20968 <at> debbugs.gnu.org
Subject: bug#20968: 25.0.50; Be able to specify the output directory for `byte-compile-file'
Date: Sat, 04 Jul 2015 21:25:22 +0300

> Date: Sat, 4 Jul 2015 11:20:05 -0700 (PDT)
> From: Drew Adams <drew.adams <at> oracle.com>
> Cc: rgm <at> gnu.org, 20968 <at> debbugs.gnu.org
> 
> > > But AFAIK, the behavior is well-defined.
> > 
> > It's well-defined only for the current behavior, where the *.el and
> > the corresponding *.elc files live in the same directory.
> 
> How so?  Please give a concrete example where it is not well-defined
> for a foo.el and a foo.elc that are in different directories.  Explain
> what problems you think arise in such a case.

I already did that: we search load-path linearly, only once, looking
for .el and .elc files in each directory.

> Can you please point out just what the problems are?

Sorry, don't have all that time.  You will have to read the code to
understand what I'm talking about.  The function 'openp' in lread.c is
the starting point, and the next step is to read the implementation of
'load'.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.