3 commits

Author	SHA1	Message	Date
Lenny Maiorani	8b334248e4	Libraries: Use default constructors/destructors in LibVT ... https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#cother-other-default-operation-rules "The compiler is more likely to get the default semantics right and you cannot implement these functions better than the compiler."	2022-03-13 22:34:38 +01:00
Andreas Kling	12a42edd13	Everywhere: codepoint => code point	2021-06-01 10:01:11 +02:00
Daniel Bertalan	be519022c3	LibVT: Implement new ANSI escape sequence parser ... This commit replaces the former, hand-written parser with a new one that can be generated automatically according to a state change diagram. The new `EscapeSequenceParser` class provides a more ergonomic interface to dealing with escape sequences. This interface has been inspired by Alacritty's [vte library](https://github.com/alacritty/vte/). I tried to avoid changing the application logic inside the `Terminal` class. While this code has not been thoroughly tested, I can't find regressions in the basic command line utilities or `vttest`. `Terminal` now displays nicer debug messages when it encounters an unknown escape sequence. Defensive programming and bounds checks have been added where we access parameters, and as a result, we can now endure 4-5 seconds of `cat /dev/urandom`. :D We generate EscapeSequenceStateMachine.h when building the in-kernel LibVT, and we assume that the file is already in place when the userland library is being built. This will probably cause problems later on, but I can't find a way to do it nicely.	2021-05-16 11:50:56 +02:00