Re: Lessons learned from string-fix and consequences on StringNg design

>> Definately. With a 32-bit signed size it _should_ be large enough for
>> most uses. A debugs when it goes close to or over the signed rollover
>> would be critical IMO. Maybe more, but debugs & assert for now.
> Do not assert(), just use Must(false) or equivalent. No reason to kill
> the proxy if the caller can simply cancel the offending transaction.
> StringNg already uses exceptions for exceptional situations and this is
> no different.

I agree. In fact, I've defined a SBufTooBigException (inheriting
TextException) for the purpose.

-- 
    /kinkie