Michael James Clift

I'm having this same issue, I know it's been 3 years but do you recall if you fixed it?

For others who are having trouble.. I had 2 problems. 1. The function I was providing for network->mqttread was not attempting to read if the timeout value passed to it...

What and where is main.h? Are you intending the user to configure dwt_delay.c by putting the necessary includes & defines in the header file for their main.c? (or whichever file...

For base, just a simple uint8_t, as there's no arithmetic performed on base which would require masking it down to 8bits on a 32bit cpu. For precision and width, uint_fast8_t...

Not 100% sure. It really comes down to opinion as to what a reasonable width limit is. Printf is generating text, 255 sounds like a reasonable limit for the width...

I fixed this in my fork (avr-progmem), commit d85de16af01808f4bde231614f05b7cc65cc7d26 Around line 430, I had to remove: if (!(flags & FLAGS_PRECISION) && len && ((len == prec) || (len == width)))...

> ... plus - just removing this results in test case failures. Have you verified all those test case checks are invalid? It didn't break any test cases. At least...

> > It didn't break any test cases. At least none that existed at the time. > > Ok, but... it breaks the "padding #20" test case on the master...

Awesome. I think I should rebase my fork from yours, thanks! On Sat, Jul 31, 2021 at 1:13 AM Eyal Rozenberg ***@***.***> wrote: > @mickjc750 : Both 0 padding and...

It looks like you are calling fctprintf() with a NULL instead of your output function. Is it your intention to discard the output?