Contents of node4

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//en">

<!–Converted with LaTeX2HTML 2022 (Released January 1, 2022) –> <HTML lang="en"> <HEAD> <TITLE>Contents of Typesetting Objects</TITLE>

<H1><A ID="SECTION00040000000000000000"> Typesetting <IMG STYLE="height: 39.24ex; vertical-align: 139.30ex; " SRC="img1.png" ALT="APL"> Objects</A> </H1>

Typing the name of an occasional APL symbol within a normal text is not a real nuisance to the author of APL texts. But typesetting a larger piece of APL code certainly is. Imagine a function named , which implements a recursive tree traversal algorithm:

In order to print just the beginning of the header of the function, you would have to type:

Obtaining the familiar function layout used in APL textbooks would require additional code. What is more, besides being awkward the whole process is error-prone: Almost certainly it will result in a printout different from the APL code.

Therefore we strongly recommend automatic translation of APL code. We provide an APL front end which transforms APL objects into logical document elements which can be <code> =</code> into LATEX documents. This guarantees consonance between the original APL code and its listing and is also more convenient.

For all APL language elements we have defined APL functions and corresponding LATEX environments. Our system supports the typesetting of:

<UL> <LI>an array displayed by the interpreter, </LI> <LI>an array in boxed representation, </LI> <LI>a function or operator displayed by the built in APL del-editor (–editor), </LI> <LI>a function or operator displayed by APL's canonical representation function , </LI> <LI>a direct definition of a function or operator, </LI> <LI>an APL expression input by the user. </LI> </UL> Apart from minor modifications we have used traditional layout conventions for all language elements. For example, the convention that user input is six spaces indented can be traced back to the very first implementation of APL. An other traditional convention states that if a line of APL code does not fit on a single line of the display, the rest of the code is wrapped around and continues on the next line. In some functions this rule may lead to line breaks in the middle of names. Since APL identifiers can be up to 255 characters long line breaking within names cannot be avoided in general.

As you can see, arrays and functions can be typeset in various ways. For example, the above listing of the APL function was printed by the following APL expression:

<IMG STYLE="height: 54.20ex; vertical-align: 124.19ex; " SRC="img5.png" ALT="
$\begin{APLbold}\begin{APLexpr} \APLquote\APLT\APLR\APLE\APLE\APLquote\APLspace\A... ...Lquote\protect\APLdelta\APLT\APLR\APLE \APLE\APLquote \end{APLexpr}\end{APLbold}$
"> The APL function produces the file <TT>tree.tex</TT> as output. The APL front end not only maps each character into the corresponding TEX macro but it also produces the line numbers in brackets and the surrounding LATEX environments in order to guarantee uniform display of functions throughout the document.

In the following we present examples for each of the cases mentioned above. At the same time, the examples give us the opportunity to demonstrate variations of type style and size.

<HR> <!–Table of Child-Links–> <A ID="CHILD_LINKS">Subsections</A>

<UL> <LI><A NAME="tex2html19" HREF="node5_ct.html" TARGET="contents">Typesetting <IMG STYLE="height: 39.24ex; vertical-align: 139.30ex; " SRC="img1.png" ALT="APL"> Arrays</A> <LI><A NAME="tex2html20" HREF="node6_mn.html" TARGET="main">Typesetting <IMG STYLE="height: 39.24ex; vertical-align: 139.30ex; " SRC="img1.png" ALT="APL"> Functions</A> <LI><A NAME="tex2html21" HREF="node7_mn.html" TARGET="main">Typesetting <IMG STYLE="height: 39.24ex; vertical-align: 139.30ex; " SRC="img1.png" ALT="APL"> Expressions</A> <LI><A NAME="tex2html22" HREF="node8_mn.html" TARGET="main">Typesetting User Dialogues and Workspaces</A> </UL> <!–End of Table of Child-Links–>

<HR>

</BODY> </HTML>;''