[ << ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Your bug reports play an essential role in making algae
reliable.
By reporting a bug, you may or may not get a timely solution to your
problem. Either way, bug reports help us to make the next version of
algae
better. In addition, your comments or criticisms on
algae
or the Algae language are also welcomed.
The algae
interpreter is incomplete. There are several operations
that it should be able to perform but that have not yet been
implemented. These cases elicit a "detour" message from algae
.
Since they're not bugs, you don't need to tell us about them. Still,
complaining about them might get them fixed.
9.1 Reporting Bugs 9.2 Reported Bugs
In order for a bug report to serve its purpose, you must include the information we need to fix it. As the GNU people say, "report all the facts". But never mind Joe Friday--the more information the better. It usually doesn't pay to explore the "envelope" of the bug; that is, changes to the input that affect it. Providing a simple example is the best way to get a bug fixed.
You should include the following information with your bug report:
algae
. You can get this by running it with the
`-V' option.
Send bug reports to:
ksh@sideslip.org |
or, as a last resort, mail them to:
Algae Bugs Attn: Scott Hunziker The Boeing Company P.O. Box 3707, MC 8K-26 Seattle, WA 98124-2207 |
Below is a list of bugs that are known to exist in the current version
of algae
and are waiting to be fixed.
algae
dumps core. For example, the
expression
function () { return self(); } () |
will not return gracefully. (I just tried it, and I had to reboot my machine!) It usually takes more than 500 levels of recursion to hit this bug, though, so you'll probably only encounter it with runaway functions.
source
function from an interactive session and encounter a parse error in the
process.
info
function may not take you to the right place in
the document.[ << ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |