Quote:
Did I missed anything? I'm not sure what this answer is really saying ... Is FMTK for such a beast?
Who said that I/O should be handled by the CPU? I mentioned it just as an example for a producer-consumer situation.
It is more the case of "Written in Assembler", that I disprove of. PDP 11 Unix all but the kernal written in C. They have had better languages out for writing OS's but they never made out in to the real world, like Simula 67. I grumble at C being revised every time IBM or INTEL comes up with a new CPU or Computer Hardware.
ADC , SBC and test Carry flag have allways been left out all High Level Languages I know of.
Enable and Disable Interupts tend to macros in C. Languages promote strange ideas like object
programming or some feature of the week. They don't make life easier for the programmer.
I can't say, Int unsigned foobar 13: bits int signed us.money.total.cents 72:bits
or List rock.groups beatles = {"john" "paul" "George" "Ringo"}.
or c = a/b if(NAN) call exit(-1)
With better hardware.
The main cpu sleeps, or runs after a timer tick or system Call.
I/O is handled in the background by little elves, not DEMONS from Hell.
The reason I don't agree with object programing you don't have objects in the first place.
You have similar data types often but you can't share them.
object car: Model A: Tank: RickShaw. they all carry people and move on roads
but very little shared data.
Ben.