Fun to read and looks like a great way to ease APL users to J.
A few suggestions:
In "A simple monadic verb (eval)" the value returned is not necessarily the
last value calculated. It is the last value not in a T-block. The only place
I could find a reference in that is in J for C Programmers in Chapter 28,
Control Structures. But I know it's somewhere else also. Perhaps putting an
"almost" in front of the "always" which is a link explaining what a T-block
is. Or just leave the "almost" hanging as a teaser to be explained later.
_____________________________________________
In "Re-defining a J word using IJX" you must have overridden the default
display format in your J session. The default format will produce something
like:
eval
+-+-+-----------+
|3|:|{. ". '0',y|
+-+-+-----------+
Also, to be consistent with earlier comments on the use "verb" instead of
"3" in an explicit definition, why not change the single line definition to:
eval=: verb : '{. ". ''0'',y'
_____________________________________________
In "Conditional statements in J, all on one line", when mentioning the APL
diamond separator you might want to clarify that the diamond separator
separates statements, where [ does not. So J assigns names right-to-left
instead of APL diamonds resulting in names assigned left-to-right. Not a
biggie, but it really took me a while to get over that hump when I started
J.
_____________________________________________
In "Keeping files of code separate" the link LoBrow brings up the WIKI
undefined page. Need to point that to your download page for LoBrow. Also,
LoBrow requires definitions from "handy.ijs". Not a problem if the reader
adds handy to their startup as well as LoBrow, but somewhere there should be
a notification that LoBrow requires handy.
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
