> On 20 Jun 2023, at 18:16, Claudio Jeker wrote:
>
> On Tue, Jun 20, 2023 at 03:35:11PM +0200, Theo Buehler wrote:
>>> On Tue, Jun 20, 2023 at 02:17:06PM +0200, Claudio Jeker wrote:
>>> Ok, this went overboard. I just wanted to clean up a bit more in
>>> check_tcp.c but noticed
On Tue, Jun 20, 2023 at 03:35:11PM +0200, Theo Buehler wrote:
> On Tue, Jun 20, 2023 at 02:17:06PM +0200, Claudio Jeker wrote:
> > Ok, this went overboard. I just wanted to clean up a bit more in
> > check_tcp.c but noticed check_send_expect and CHECK_BINSEND_EXPECT.
> >
> > This code is not very
On Tue, Jun 20, 2023 at 02:17:06PM +0200, Claudio Jeker wrote:
> Ok, this went overboard. I just wanted to clean up a bit more in
> check_tcp.c but noticed check_send_expect and CHECK_BINSEND_EXPECT.
>
> This code is not very consitent in the differnt ways the strings are
> encoded. Especially
Ok, this went overboard. I just wanted to clean up a bit more in
check_tcp.c but noticed check_send_expect and CHECK_BINSEND_EXPECT.
This code is not very consitent in the differnt ways the strings are
encoded. Especially check_send_expect() is a bit of a mess because of
that.
While there I