@alanc Nice work! These are also becoming common for some distros:
https://best.openssf.org/Compiler-Hardening-Guides/Compiler-Options-Hardening-Guide-for-C-and-C++.html
@jani I’ve been doing ZMODEM that was also a thing in the 90s :-) https://github.com/jarkkojs/zmodem2
I guess this is sort of retro modern project :-)
Just want to sort out the issue of difficult file transfers when you have only a serial cable access and get a basic serial terminal with nothing special except file transfers of which progress you can see and also cancel them. It is 2023 and we still have to curse lrzsz
so it is better to fix that issue…
I mean I had a decent experience with ZMODEM last time when using MS-DOS and software such as Telemate and Telex.
I have also TUI client in progress but had to halt that because could not find an appropriate crate with decent quality.
generated documentation starts to look a bit like actual documentation after fixing all the clippy::pedantic
errors.i was not aware of this flag until some sent a PR fixing a few of these. not that experienced with the language yet..
only thing that is left is two integration tests for examples in order call this 0.1, i.e. test_sz_to_rzm
and test_rz_szm
but I need a. stable and idiomatic way to point out to the executables. I guess I could make this happen by injecting stuff through build.rs
, right?
after that is sorted out it is good for what i needed it originally for (my serial terminal), i’ll set up github runner for CI (tests + clippy), make the crate release and call it a day. after that not going to do proactively do anything to it except review and merge pull requests.