mirror of
https://git.tartarus.org/simon/putty.git
synced 2025-03-12 18:13:50 -05:00
be0cea7130
There's no actual need to copy the data from term->inbuf into a local variable inside term_out(). We can simply store a pointer and length, and use the data _in situ_ - as long as we remember how much of it we've used, and bufchain_consume() it when the routine exits. Getting rid of that awkward and size-limited local array should marginally improve performance. But also, it opens up the possibility to suddenly suspend handling of terminal data and leave everything not yet processed in the bufchain, because now we never remove anything from the bufchain until _after_ it's been processed, so there's no need to awkwardly push the unused segment of localbuf[] back on to the front of the bufchain if we need to do that. NFC, but as usual, I have a plan to use the new capability in a followup commit.
This is the README for PuTTY, a free Windows and Unix Telnet and SSH
client.
PuTTY is built using CMake <https://cmake.org/>. To compile in the
simplest way (on any of Linux, Windows or Mac), run these commands in
the source directory:
cmake .
cmake --build .
Documentation (in various formats including Windows Help and Unix
`man' pages) is built from the Halibut (`.but') files in the `doc'
subdirectory using `doc/Makefile'. If you aren't using one of our
source snapshots, you'll need to do this yourself. Halibut can be
found at <https://www.chiark.greenend.org.uk/~sgtatham/halibut/>.
The PuTTY home web site is
https://www.chiark.greenend.org.uk/~sgtatham/putty/
If you want to send bug reports or feature requests, please read the
Feedback section of the web site before doing so. Sending one-line
reports saying `it doesn't work' will waste your time as much as
ours.
See the file LICENCE for the licence conditions.