Martin Rubey wrote:
> 
> Dear all,
> 
> in sbcl based FriCAS, I get style warnings when first using the HyperDoc 
> Browse
> facility.  For the emacs mode, I need to make them go away.  How can I do 
> that?
> 
> I tried
> 
>  )lisp (declaim (sb-ext:muffle-conditions warning))
> 
> within FriCAS (before triggering the autoload), but it didn't seem to help.
> 
> Is the reason that triggers the warnings, that they are first symbols (in
> util.lisp, because of the setq), and then become functions?
> 
> Martin
> 
> STYLE-WARNING: redefining |bcMatrix| in DEFUN
> STYLE-WARNING: redefining |bcIndefiniteIntegrate| in DEFUN

1) The warning says what happens: several functions is redefined.
  At startup functions like bcMatrix are just stubs: calling bcMatrix
  triggers loading of hyperdoc.  Loading means that old definition of
  bcMatrix is replaced by the new one.
2) Simple method to avoid problem with HyperDoc is to load it before
  doing anything else (by calling |browserAutoloadOnceTrigger|).  Note
  that algebra also uses autoloading, so you may still get the same
  problem from algebra.  Also other autoloade parts may be problematic.
3) In sbcl style warning is not a warning, so you need a separate
  construct -- this is clearly explained in sbcl manual (I forgot
  explanation, but I remember that it is there).
4) In the past Axiom simply redirected all diagnostics to special
  stream so they were all ignored.  I _really_ do not want to this:
  once diagnostics are redirected program may die or hang with no
  clue to users what happened.

-- 
                              Waldek Hebisch
[EMAIL PROTECTED] 

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"FriCAS - computer algebra system" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/fricas-devel?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to