Dear Tim,
there is a new extension to the syntax to add examples. Essentially
any line that begins with ++E will be output as Example documentation
to the display command. So the coerce from Tuple now reads:
coerce: PrimitiveArray S - %
++ coerce(a) makes a tuple from primitive
there is a new extension to the syntax to add examples. Essentially
any line that begins with ++E will be output as Example documentation
to the display command. So the coerce from Tuple now reads:
coerce: PrimitiveArray S - %
++ coerce(a) makes a tuple from primitive array a
Ideally the user just runs bugreport and everything gets sent to
us.
Note that people want to see what gets sent to a remote site. No system
nowadays sends any information of the user system automatically, but
rather pop up a window. See for example how bugs are sent in firefox.
Ralf
You could also move some checking time to the users machine. At the time
the documentation is rendered, the commands in ++E are executed and
compared internally with the ++R stuff.
Since execution might take some time, first show the ++R output and
spawn a background process that compares the
But you remember there were pages in hyperdoc that could be explicitly
executed by pressing a button. So if that is connected to ++E and ++R
that would not be a problem, because the user asked for it. Well of
course, you must check that the user did not modify the ++E stuff before
you compare
Ideally the user just runs bugreport and everything gets sent to
us.
Note that people want to see what gets sent to a remote site. No system
nowadays sends any information of the user system automatically, but
rather pop up a window. See for example how bugs are sent in firefox.
Oh,
process to filter out the ++E/++R testing syntax lines automatically.
The only thing where I am not so sure about is whether ++E/++R is the
best syntax. As you may have seen in the ++ or +++ documentation, some
people dont put a space after the last + so you parser might get confused.
One hole in the documentation layering is that the )help files
should show examples of the use of every function in the export list.
This is currently not the case and I'll look at fixing that as part
of the display test cases.
Tim
___
Axiom-developer
There is bug automation in firefox? Interesting. Perhaps I can use
the same mechanism in the new firefox frontend.
Well, you have to wait until your firefox crashes... which happened a
couple of times to me.
Ralf
___
Axiom-developer mailing list
The following exposed functions now have )display op documentation:
CartesianTensor: ravel, leviCivitaSymbol, *, kroneckerDelta, reindex,
transpose, contract, product, elt, rank, coerce
CardinalNumber: -, **, generalizedContinuumHypothesisAssumed,
Demo the Axiom type towers.
===
diff --git a/changelog b/changelog
index f2bd54b..04a4914 100644
--- a/changelog
+++ b/changelog
@@ -1,3 +1,5 @@
+20080818 tpd src/input/Makefile typetower.input added
+20080818 rhx src/input
I am getting increasingly interested in literate programming. There are a
few questionmarks I am turning at the idea of turning the aldor compiler
sources into literate programs.
I have a long term interest in making Aldor be literate when it
becomes part of Axiom. If the code had been released
--git a/changelog b/changelog
index 04a4914..377aa85 100644
--- a/changelog
+++ b/changelog
@@ -1,3 +1,13 @@
+20080818 tpd src/input/Makefile biquat.input added
+20080818 dxc src/input/biquat.input added
+20080818 dxc David Cyganski (no known email)
+20080818 tpd src/input/Makefile ifthenelse.input
13 matches
Mail list logo
