On Fri, Mar 21, 2014 at 5:54 AM, Bjoern Hoehrmann <derhoermi@gmx.net> wrote:
> * Nicolas Mailhot wrote:
> >Really, can't you read the abundant documentation that was written on the
> >massive FAIL duck typing is for encoding (for example, python-side)? Code
> >passing unit tests then failing right and left as soon as some new
> >encoding combo or text triggering encoding differences injected in the
> >system? Piles of piles of partial workarounds till there was complete loss
> >of understanding how they were all supposed to work in the first place?
> >
> >That's the last thing you want to reinvent on security equipments (and
> >you'll reinvent it because the amount of non-ASCII urls is small now but
> >will only grow with time).
>
> Julian asked for a concrete example use case. So far you have not given
> one. It might help to assume the rest of us understands the subject at
> hand at least as well as you do.
>
I too am wondering this.
In general, this just sounds like "more stuff".
I'm not aware of anyone having real-world problems which this solves. It
would be very helpful if those real cases were enumerated.
Mike
> --
> Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
> Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
> 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
>
>