- 3.1
- Type it in and
comprehend the comments. I took three weeks of spare
time.
- 3.2
- The block size is 512 for a VMatrix.
This allows a 32 meg memory buffer
- 5.1
- It appears a bit
heavy handed with all of the casts to long ints, but there
were some problems of improper type promotion encountered
during development.
- 5.2
- This ability to operate on the hdr of
vdoub clarified the meaning of inheritance for me since a
VMatrix is really just a virtual vector with some extra
functionality. It also shows why the hdr must be protected
rather than private in vdoub.
- 5.3
- If you force a zero division in this
routine, VAX CC will cause a print of the function call
sequence to the error output stream
- 6.1
- I cannot see a reason for
directly allocating another MStack other than Dispatch,
since the matrix functions push their results onto
Dispatch. Maybe someone with a parallel processor
would want several independent stacks, but the rest of the
program would have to be rewritten. The vmm system would
need to be scrapped too. It's clear YAMP is a PC program
- 6.2
- By the way, just what is
this, a statement or a function call?
- 7.1
- This is one of my disappointments with C++. I
would have preferred to overload a postfix operator, say `,
for the transpose, but such an operator does not exist in
C++. So what, I never intended to write APL.
- 9.1
-
This is an example of the design by differences concept that is
making C++ so popular
- D.1
- My Christmas present from my wife
was the time to do this over the holiday vacation.