axiom-developer
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Axiom-developer] [#77 protected-symbol-warn called with (NIL)] nocompil


From: Bill Page
Subject: [Axiom-developer] [#77 protected-symbol-warn called with (NIL)] nocompil.lisp.pamphlet
Date: Tue, 25 Jan 2005 11:07:20 -0600

says::

  The function **protected-symbol-warn** was added because it is
  used in **setvart.boot** but apparently is nowhere defined. It
  is probably primitive to **CCL**.

  The function **protect-symbols** was added because it is
  used in **setvart.boot** but apparently is nowhere defined. It
  is probably primitive to **CCL**

However **setvart.boot** does not actually referenced in
**protected-symbol-warn**

<<gcl-cmpnote>>::

  (in-package "BOOT")
  (defun protected-symbol-warn (&rest arg))
  ;  (format t "protected-symbol-warn called with ~A~%" arg))
  (defun protect-symbols (&rest arg))
  ;  (format t "protected-symbol-warn called with ~A~%" arg))

  ...

  (defun enable-backtrace (&rest arg)
    (format t "protected-symbol-warn called with ~A~%" arg))

-----

Perhaps enable-backtrace is what issues the message.
What is this really supposed to do? In the case of CCL
t seems to be called from **debug.lisp.pamphlet** ::

  A "resumable" break loop for use in trace etc. Unfortunately this
  only works for CCL. We need to define a Common Lisp version. For
  now the function is defined but does nothing.
  <<interrupt>>=
  #-:CCL
  (defun interrupt (&rest ignore))

  #+:CCL
  (defun interrupt (&rest ignore)
    (prog (prompt ifile ofile u v)
      (setq ifile (rds *debug-io*))
      (setq ofile (wrs *debug-io*))
      (setq prompt (setpchar "Break loop (:? for help)> ")) top (setq u (read))
      (cond
        ((equal u ':x) (go exit))
        ((equal u ':r) (go resume))
        ((equal u ':q)
          (progn (lisp::enable-backtrace nil)
  ...

-------

This is the only place I can find that would call a function
that prints this error message. Could the conditional be
somehow ignored?

It's a mystery.

Also, at least on the Windows version of Axiom::

  )set kernel protect on

and::

  )set kernel warn on

seem to be non-functional, i.e.::

  )set kernel

still shows both in the 'off' state.
--
forwarded from http://page.axiom-developer.org/zope/mathaction/address@hidden




reply via email to

[Prev in Thread] Current Thread [Next in Thread]