Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
In this example, one function serves to sum the elements<br />
in arrays of different types. This is not possible in Apple II<br />
Pascal, so any programs on the Apple/// would have to be<br />
modified for use on the II.<br />
UCSD Pascal, Version IV<br />
Where do I begin? Get this:<br />
In General:<br />
* Compiler option selectable native code generation;<br />
A third difference between the Pascals is the larger<br />
number of effective segments allowed in the Apple // /<br />
program. Each such program is permitted 16 segments or<br />
regular units, 16 units from the System Library, and 16<br />
intrinsic units from a program library for a total of 48 segments<br />
or units! If you get accustomed to this feature, you<br />
will have trouble moving your programs to an Apple II.<br />
* Double precision real arithmetic;<br />
* An enhanced System Editor including "tabstop," "exchange<br />
delete," and "exchange insert" commands;<br />
* Complete freedom to redirect program and system 1-0<br />
from the X( ecute command line and from within programs;<br />
* Up to 256 units or segments per program, all units intrinsic,<br />
no linking;<br />
One way to solve potential portability problems is to<br />
program to the lowest common denominator; to not use<br />
the" new" features of the more powerful machines. Another<br />
way is to abandon the Apple II entirely; after all, you probably<br />
so.Id it to get the money to buy the ///, right? Better, in my<br />
opinion, would be to implement these features for the II.<br />
(C'mon, guys, you can do it!) Arid while we're at it, why not<br />
kick in a type "realstream," or better yet, conformant arrays,<br />
the generalization of these "streams."<br />
* A program's units can reside in any library;<br />
* Every library has room for 256 units;<br />
* File variables allowed in the interface section of units,<br />
segment procedures allowed in the implementation section<br />
(not possible in the Apple Pascals);<br />
* Units can use other units in their implementation section<br />
as well as in their interface;<br />
* Turtlegraphics. Not source code compatible with Apple's.<br />
Some of my friends rather strongly disagree with me<br />
here. They like what they have on the II, and aren't interested<br />
in seeing it changed. You may agree with them. In fact, you<br />
may not care at all. Again, it depends on you and your goals.<br />
* Chaining;<br />
* A " screen ops" unit to control the screen, including access<br />
to the system date;<br />
78 Apple Orchard