Timeline for FIFO getch/ungetch Functions
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 2, 2021 at 3:00 | history | tweeted | twitter.com/StackCodeReview/status/1356437198380429313 | ||
| Nov 11, 2015 at 16:31 | vote | accept | LastSecondsToLive | ||
| Nov 11, 2015 at 5:24 | comment | added | 200_success | Note that the curses library has an ungetch() function. It sidesteps the FIFO-vs.-LIFO issue by guaranteeing a buffer of just one character; the behaviour of a second successive ungetch() call is undefined. | |
| Nov 11, 2015 at 0:33 | answer | added | Deduplicator | timeline score: 0 | |
| Nov 10, 2015 at 23:52 | answer | added | 200_success | timeline score: 2 | |
| Nov 10, 2015 at 23:22 | history | edited | 200_success | CC BY-SA 3.0 | deleted 8 characters in body; edited tags; edited title |
| Nov 10, 2015 at 23:02 | comment | added | Deduplicator | Then you push it back byte-for-byte, in the reverse order you read it. | |
| Nov 10, 2015 at 22:21 | comment | added | LastSecondsToLive | But what if I read a whole word in and want to push it back into input? | |
| Nov 10, 2015 at 21:46 | comment | added | Deduplicator | Well, ungetch undoes a single getch. It doesn't make sense to undo an operation before you undid whatever else you did afterwards.... | |
| Nov 10, 2015 at 20:58 | history | asked | LastSecondsToLive | CC BY-SA 3.0 |