#UCSD Units vs M2
3 messages in this thread
I agree with you that termination code is nice to have. The M2Amiga
package has that feature, and I'm told that Benchmark will probably have it
in the next release (no release dates yet). In the meantime, you can use
my termination module (I have one for Benchmark and one for TDI), which
will basically accomplish the same thing. It appeared in an article in
Amazing Computing some time ago.
By the way, an earlier version of UCSD Pascal for the Amiga was reviewed by
a colleague of mine (and Richie's) for Ami Project (an apparently defunct
magazine). To quote the review, UCSD Pascal is "… a giant leap
backwards." It took over the machine, killing multitasking, and access to
ROM Kernel routines was abysmal. – Steve –
No question about it, UCSD Pascal uses the Amiga as a glass teletype, but the
code I wrote on my Sage IV ran unaltered (except for the call to the system
clock). Me and Infocom.
I feel I would be remiss if I did not point out that while it is true that
UCSD Pascal shut down AmigaDOS pretty thoroughly and hence Amiga
multi=tasking, it does offer multi-tasking within a UCSD Pascal program
through the use of PROCESS & SEMAPHORE. In fact, Occam, the language of
the Transputer, was implemented/designed in UCSD Pascal just because it was
deemed such a swell multi-tasking language by the Transputer folks.
MetaComCo released Tripos for the Sage, whose native operating system was
UCSD, about three years before they released child-of-Tripos for the Amiga,
so it is not inconceivable that some of the multitasking ideas implemented
in AmigaDOS were inspired by good ol' Sage Pascal.