Displaying 2 results from an estimated 2 matches for "prii8".
Did you mean:
pii8
2019 Sep 23
2
[PATCH nbdkit v2] server: public: Add nbdkit_parse_* functions for safely parsing integers.
...AX */
+ PARSE (unsigned, "%u", "-2147483648", BAD); /* INT_MIN */
+ PARSE (unsigned, "%u", "0x7fffffff", OK, 0x7fffffff);
+ PARSE (unsigned, "%u", "-0x80000000", BAD);
+
+ /* Test nbdkit_parse_int8_t. */
+ PARSE (int8_t, "%" PRIi8, "0", OK, 0);
+ PARSE (int8_t, "%" PRIi8, "0x7f", OK, 0x7f);
+ PARSE (int8_t, "%" PRIi8, "-0x80", OK, -0x80);
+ PARSE (int8_t, "%" PRIi8, "0x80", BAD);
+ PARSE (int8_t, "%" PRIi8, "-0x81", BAD);
+
+...
2019 Sep 23
2
Re: [PATCH nbdkit] server: public: Add nbdkit_parse_* functions for safely parsing integers.
On Mon, Sep 23, 2019 at 12:05:11PM -0500, Eric Blake wrote:
> > + int nbdkit_parse_long (const char *what, const char *str, long *r);
> > + int nbdkit_parse_unsigned_long (const char *what,
> > + const char *str, unsigned long *r);
>
> Do we really want to encourage the use of parse_long and
> parse_unsigned_long? Those differ between