[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Axiom-developer] [debugging Axiom]
From: |
kratt6 |
Subject: |
[Axiom-developer] [debugging Axiom] |
Date: |
Tue, 08 Nov 2005 08:22:08 -0600 |
Changes http://page.axiom-developer.org/zope/mathaction/DebuggingAxiom/diff
--
??changed:
-Fortunately, Axiom is rather easy to debug. Most of the source is very
transparent, so once you have localized the bug there are mostly
-"design issues":DesignIssues to overcome. However, to find out which function
is bugged, there are some helpful tools. Let's use the following might-be-bug
as a running example:
Fortunately, Axiom is rather easy to debug. Most of the source is very
transparent, so once you have localized the bug there are mostly "design
issues":DesignIssues to overcome. However, to find out which function is
bugged, there are some helpful tools.
These consist of:
- inspecting signatures of operations and packages, domains and categories
using::
)display operation foo
)show mydomain
- seeing which functions are called using ')set message bottom on'
- using the "trace facility":HyperDocTracing
Let's use the following might-be-bug as a running example:
--
forwarded from http://page.axiom-developer.org/zope/mathaction/address@hidden
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Axiom-developer] [debugging Axiom],
kratt6 <=