Some documenting of load-prefer-newer

* doc/lispref/loading.texi (How Programs Do Loading, Load Suffixes):
Mention `load-prefer-newer'.

* src/lread.c (Fload): Mention load-prefer-newer in doc.

2 files changed, 8 insertions, 0 deletions

diff --git a/src/ChangeLog b/src/ChangeLog
index 6e0a01bcbae..8a521a585b6 100644
--- a/src/ChangeLog
+++ b/src/ChangeLog
@@ -1,3 +1,7 @@
+2013-12-23  Glenn Morris  <rgm@gnu.org>
+
+        * lread.c (Fload): Mention load-prefer-newer in doc.
+
 2013-12-22  Martin Rudalics  <rudalics@gmx.at>
 
         Handle Bug#16207 by being more restrictive when running hooks.
diff --git a/src/lread.c b/src/lread.c
index 1db3a47ef0a..a6181b0cb85 100644
--- a/src/lread.c
+++ b/src/lread.c
@@ -1029,6 +1029,10 @@ in `load-file-rep-suffixes'.  If MUST-SUFFIX is non-nil, only the
 return value of `get-load-suffixes' is used, i.e. the file name is
 required to have a non-empty suffix.
 
+When searching suffixes, this function normally stops at the first
+one that exists.  If the option `load-prefer-newer' is non-nil,
+however, it tries all suffixes, and uses whichever file is the newest.
+
 Loading a file records its definitions, and its `provide' and
 `require' calls, in an element of `load-history' whose
 car is the file name loaded.  See `load-history'.