Overflow check in encoder differs from RFC3492?

Nobody has claimed this yet.

Hi,

I find that the JS implementation of the `toASCII()` encoder here closely resembles the C sample implementation in the RFC3492 specification, except the following:

In https://github.com/bestiejs/punycode.js/blob/702cc2daf10a5b97454666069e146d04745af728/punycode.js#L409,

``` javascript
if (currentValue < n && ++delta > maxInt) {
error('overflow');
}
```

In https://tools.ietf.org/html/rfc3492#page-27,

``` c
if (input[j] < n /* || basic(input[j]) */ ) {
if (++delta == 0) return punycode_overflow;
}
```

In particular, the JS version is checking `++delta` against whether it's larger than `maxInt`, whereas the C version is checking against whether it's equal to `0`. Is this intended, or have I missed anything when reading your code? Any clues?

Thanks!

Start at punycode.js line 409 and compare the JavaScript overflow condition with the C sample on RFC 3492 page 27. Determine whether the differing checks are intentional and verify the encoder’s behavior for values near the overflow boundary; done means the discrepancy is resolved with a clear explanation or correction.

Written by the indexing model from the issue text.