Hey guys, sorry, I should have put a big smiley on the end of "How do you set a bit in an I/O port in APL?". It was said with tongue firmly stuck in cheek.
It was my way of saying that my simple mind needs languages that I can relate to the concrete reality of bits , bytes, memory and I/O etc. The far way mathematical abstractions of APL are too much for me.
Having said that, on reflection, why should a language like APL not do such things? I might not expect a PLC to do million node FEA but certainly small embedded systems are doing serious filtering, FFT, image analysis and other DSP tasks on large data sets of arrays and matrices whist at the same time needing to be interfaced to the real-world they are monitoring/controlling.
Perhaps an APL like language that expresses those algorithms more succinctly but also understands real-world I/O would be a great help to those designers of such systems who are currently using C/C++.
It could be that some modern implementations are but I think APL predates C. My guess is that the first versions of APL were either written in assembly language or Fortran.
Comments
It was my way of saying that my simple mind needs languages that I can relate to the concrete reality of bits , bytes, memory and I/O etc. The far way mathematical abstractions of APL are too much for me.
Having said that, on reflection, why should a language like APL not do such things? I might not expect a PLC to do million node FEA but certainly small embedded systems are doing serious filtering, FFT, image analysis and other DSP tasks on large data sets of arrays and matrices whist at the same time needing to be interfaced to the real-world they are monitoring/controlling.
Perhaps an APL like language that expresses those algorithms more succinctly but also understands real-world I/O would be a great help to those designers of such systems who are currently using C/C++.
It was never intended for that kind of thing, but I am sure it could have been added. After all it did receive and send bytes to a terminal.