Allow defmacros and defuns to co-exist.

Already we have the situation that there is an if function and
an if macro, and same for and and or.

This change allows such situations to be programmer-defined.

* eval.c (op_defun): Don't remhash the name from the toplevel
macro bindings.
(op-defmacro): Don't remhash the name from the toplevel
function bindings.

* txr.1: Document the permissive behavior as dialect notes
under defmacro and defun.

1 files changed, 14 insertions, 0 deletions

diff --git a/txr.1 b/txr.1
index eb328c41..18ef4813 100644
--- a/txr.1
+++ b/txr.1
@@ -10964,6 +10964,13 @@ syntax.
 In ANSI Common Lisp, keywords may be used as function names.
 In TXR Lisp, they may not.
 
+.TP* "Dialect Note:"
+A function defined by
+.code defun
+may co-exist with a macro defined by
+.codn defmacro .
+This is not permitted in ANSI Common Lisp.
+
 .coNP Operator @ lambda
 .synb
 .mets (lambda <> ( param * [: << opt-param *] [. << rest-param ])
@@ -23202,6 +23209,13 @@ The return value of the macro is the macro expansion. It is substituted in
 place of the entire macro call form. That form is then expanded again;
 it may itself be another macro call, or contain more macro calls.
 
+.TP* "Dialect Note:"
+A macro in the global namespace introduced by
+.code defmacro
+may co-exist with a function of the same name introduced by
+.codn defun .
+This is not permitted in ANSI Common Lisp.
+
 .TP* Example:
 
 .cblk