Commit 38f88a7f authored by Eli Zaretskii's avatar Eli Zaretskii

Document that generic functions cannot be commands

* doc/lispref/commands.texi (Defining Commands):
* doc/lispref/functions.texi (Generic Functions): Document
that generic functions cannot be turned into commands.
parent 5aeddfac
......@@ -136,6 +136,9 @@ start with a capital, e.g., @code{"use (system-name) instead."}); @code{t}; any
other symbol, which should be an alternative function to use in Lisp
Generic functions (@pxref{Generic Functions}) cannot be turned into
commands by adding the @code{interactive} form to them.
* Using Interactive:: General rules for @code{interactive}.
* Interactive Codes:: The standard letter-codes for reading arguments
......@@ -1345,6 +1345,13 @@ to invoke the other auxiliary or primary methods.
This allows you to add more methods, distinguished by @var{string},
for the same specializers and qualifiers.
@end table
Functions defined using @code{cl-defmethod} cannot be made
interactive, i.e.@: commands (@pxref{Defining Commands}), by adding
the @code{interactive} form to them. If you need a polymorphic
command, we recommend defining a normal command that calls a
polymorphic function defined via @code{cl-defgeneric} and
@end defmac
@cindex dispatch of methods for generic function
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment