mirror of
https://git.savannah.gnu.org/git/guile.git
synced 2025-06-26 05:00:28 +02:00
New module (oop goops keyword-formals)
This module replaces the method and define-method bindings with their method* and define-method* counterparts, for use by users who prefer not to use both kinds of syntactic forms. * module/oop/goops/keyword-formals.scm: New module. * am/bootstrap.am: Added * doc/ref/goops.texi: Document this change.
This commit is contained in:
parent
a3c77cb8da
commit
fe05646f7c
3 changed files with 63 additions and 0 deletions
|
@ -954,11 +954,39 @@ the rest argument, as for @code{define*}.
|
|||
@end deffn
|
||||
|
||||
@menu
|
||||
* Advanced argument handling in method and define-method::
|
||||
* Type dispatch and redefinition for advanced argument handling::
|
||||
* next-method call in method*::
|
||||
* Advanced argument handling design choices::
|
||||
@end menu
|
||||
|
||||
@node Advanced argument handling in method and define-method
|
||||
@subsubsection Advanced argument handling in method and define-method
|
||||
|
||||
Some users may find it more natural not to have to choose between
|
||||
@code{define-method} and @code{define-method*} in their code.
|
||||
|
||||
It turns out that @code{method*} and @code{define-method*} can do just
|
||||
fine also for ordinary methods without keyword formals. They take
|
||||
marginally longer to compile but result in the same code as
|
||||
@code{method} and @code{define-method} if keyword formals are absent.
|
||||
|
||||
For this reason, we provide a module (oop goops keyword-formals) which
|
||||
replaces the standard @code{method} and @code{define-method} bindings
|
||||
with their keyword formal counterparts. It can be used like this:
|
||||
|
||||
@lisp
|
||||
(use-modules (oop goops) (oop goops keyword-formals))
|
||||
@end lisp
|
||||
|
||||
or
|
||||
|
||||
@lisp
|
||||
(define-module (foo)
|
||||
#:use-module (oop goops)
|
||||
#:use-module (oop goops keyword-formals))
|
||||
@end lisp
|
||||
|
||||
@node Type dispatch and redefinition for advanced argument handling
|
||||
@subsubsection Type dispatch and redefinition for advanced argument handling
|
||||
|
||||
|
@ -1082,6 +1110,9 @@ to only provide the simpler functionality (through @code{method} and
|
|||
@code{define-method}).
|
||||
@end enumerate
|
||||
|
||||
However, note that users who prefer to only use @code{define-method} can
|
||||
do so. @xref{Advanced argument handling in method and define-method}.
|
||||
|
||||
Second, we have chosen not to do type dispatch on optional or keyword
|
||||
arguments. Reasons include:
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue