Where should the type information be 176

I have also looked briefly at J, and it could even do some of the macro generation I would like, but it still does not seem like the right approach.

I am aware with what could be done as Terje suggested, even to seeing how to code it on the CYBER 205, using their particular instructions. It is not too efficient, but much better than anything I can do on the other machines whose instructions are not as suitable.

I am aware of these problems.

One can use a "variables designation" for registers, and get around this by using overloaded operators. I thought I knew what SIMD is, but what is "SIMD add"?

Also, there are many times when I want to use registers in a multiplicity of ways. I have no problems with this, even though it scares the believers in strong typing.

Even if a separate line is needed, this is no reason to have to type out a huge number of characters for each instruction. If I can only put a = b - c on a line, so be it. But I do not want to have to type

SUBINT3 c, b, a

or whatever the mnemonics and order of the arguments are for the particular buttembler involved.

This is not that far from what I want, but I still want conciseness. If Archimedes had the conciseness which comes with the use of variables, he might well have come up with calculus. This is the problem with the present buttemblers, and with languages like Lisp.

Python gets close to that. When I use

-- This address is for information only. I do not claim that these views are those of the Statistics Department or of Purdue University. Herman Rubin, Department of Statistics, Purdue University