Re: require/3 compatibility
- From: Adrian Aichner <adrian@xxxxxxxxxx>
- Date: Sat, 11 Mar 2006 11:01:00 +0100
Steve Kelem <s_kelem@xxxxxxxxxxx> writes:
I'm trying to switch over from Gnu emacs-21.3 to Xemacs-21.4.19.
Many lisp files contain code that looks like:
Which lisp files are these?
Are they under your control?
One way to handle this is to intercept the wrong-number-of-arguments
error:
(condition-case nil
(require 'thingatpt nil t)
(wrong-number-of-arguments (require 'thingatpt nil)))
Hope this helps,
Adrian
(require 'thingatpt nil t)
This works in emacs-21.3, but in Xemacs-21.4.19, I get the message:
Wrong number of arguments: require, 3
21.3 has a built-in require:
require is a built-in function.
(require FEATURE &optional FILENAME NOERROR)
If feature FEATURE is not loaded, load it from FILENAME.
If FEATURE is not a member of the list `features', then the feature
is not loaded; so load the file FILENAME.
If FILENAME is omitted, the printname of FEATURE is used as the file name,
and `load' will try to load this name appended with the suffix `.elc',
`.el' or the unmodified name, in that order.
If the optional third argument NOERROR is non-nil,
then return nil if the file is not found instead of signaling an error.
Normally the return value is FEATURE.
The normal messages at start and end of loading FILENAME are suppressed.
Xemacs-21.4.19 has:
`require' is a built-in function
(require FEATURE &optional FILENAME)
Documentation:
If feature FEATURE is not loaded, load it from FILENAME.
If FEATURE is not a member of the list `features', then the feature
is not loaded; so load the file FILENAME.
If FILENAME is omitted, the printname of FEATURE is used as the file name.
What do I need to to to get this to work?
Thanks,
Steve
--
Adrian Aichner
mailto:adrian@xxxxxxxxxx
http://www.xemacs.org/
.
- References:
- require/3 compatibility
- From: Steve Kelem
- require/3 compatibility
- Prev by Date: Re: execute "make", working directory?
- Next by Date: Re: slash v.s. backwards slash
- Previous by thread: require/3 compatibility
- Next by thread: slash v.s. backwards slash
- Index(es):
Relevant Pages
|
Loading