Talk:GET

When a char from the keyboard cache has been read, there will be space in the cache for one more char. The keyboard cache can store at most 10 chars (by default), further input chars are ignored.

I am confused about this part.

I used an emulator to GET A$ and GET A. In both cases it did not wait for a keypress, it continued past the GET in a fashion similar to INKEY$. In the example code on this page I see it looping back to the GET if the ASCII is zero, which seems to imply this is how it should work.

So I am a bit mystified how the buffer might ever have more than one character in it?

--Maury Markowitz (talk) 15:22, 4 December 2024 (CET)