From: list at eworm.de (Christian Hesse)
Subject: [PATCH 1/1] cgitrc: handle value "0" for max-repo-count
Date: Fri, 23 Nov 2018 17:08:31 +0100 [thread overview]
Message-ID: <20181123170831.4904c09f@leda> (raw)
In-Reply-To: <CAHmME9rN-p2wQzgq7GROR9whSuOCWDfOVTNhcdKS-oyw47sj9w@mail.gmail.com>
"Jason A. Donenfeld" <Jason at zx2c4.com> on Fri, 2018/10/19 00:52:
> Hey Christian,
>
> We should indeed introduce some sanitation helpers to deal with these
> in the general case. API suggestion:
>
> type_t parse_int(const char *str, type_t min, type_t max, type_t
> fallback_if_invalid);
>
> What would you think of that?
My intention was to add a special value 0. How about this?
type_t parse_int(const char *str, type_t min, type_t max, type_t
default_if_zero, type_t fallback_if_invalid);
--
main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH"
"CX:;",b;for(a/* Best regards my address: */=0;b=c[a++];)
putchar(b-1/(/* Chris cc -ox -xc - && ./x */b/42*2-3)*42);}
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20181123/187b1fe9/attachment.asc>
next prev parent reply other threads:[~2018-11-23 16:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 14:38 list
2018-07-16 14:41 ` list
2018-09-11 6:56 ` list
2018-10-18 22:52 ` Jason
2018-11-23 16:08 ` list [this message]
2018-12-07 4:10 ` Jason
2019-01-07 15:34 ` list
2019-01-07 15:35 ` [PATCH 1/2] cgit: introduce parse_{bool, int}() for for cgitrc parsing list
2019-01-07 15:35 ` [PATCH 2/2] cgit: sanitize max-repo-count list
2019-01-07 20:54 ` [PATCH 1/2] cgit: introduce parse_{bool, int}() for for cgitrc parsing list
2019-01-08 14:05 ` whydoubt
2019-01-10 19:23 ` [PATCH 1/1] cgitrc: handle value "0" for max-repo-count tlatorre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181123170831.4904c09f@leda \
--to=cgit@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).