Revert to RFC code: use punycode_uint and enum punycode_status.
commit4378b6813465851f46f1dda57ea7b337dbbea515
authorSimon Josefsson <simon@josefsson.org>
Wed, 13 Aug 2003 15:54:47 +0000 (13 15:54 +0000)
committerSimon Josefsson <simon@josefsson.org>
Wed, 13 Aug 2003 15:54:47 +0000 (13 15:54 +0000)
treeb5b4d885dd9448b4ff1f225f18cd6f82aab6912b
parentc48c6793c9599b4af1f028d6d468c2f55fa6f8a8
Revert to RFC code: use punycode_uint and enum punycode_status.
However, we do continue to use size_t to promote use of sizeof() by
application writers.  We return punycode_bad_input if a size_t value
exceeds the largest punycode_uint, since the code presumably cannot
handle that.  If size_t is smaller than punycode_uint, it seems
unlikely that an application could be able to pass a string that is
longer than SIZE_MAX anyway, but should it happen the worst that occur
is that the punycode code will only see the beginning of the string,
which isn't unreasonable on a platform with a small SIZE_MAX.
punycode.c