[NUG] API 2.0

[Norman Palardy]

> On Mar 13, 2019, at 4:32 PM, Tim Streater <timstreater at greenbee.net> wrote:
> 
> This was another thing it took me a long time to figure out how to make work, which also pushed me towards doing things in a memoryblock at the bottom. It's all very well getting exceptions because the text you have is illegal UTF8 but that's hardly my fault if that's what the other end sent me while at the same time swearing up and down that it *is* UTF8. Fortunately I found the lossy conversion flag.

It is troublesome when the other end doesn't actually send you what it says its sending you

This is one of those things you had no hope of handling correctly with "string" because it just willingly took in bytes and you could define the encoding and it would just try & do it - no errors nothing if things were bogus

Like I said - everything in the new framework had a reason & purpose but .. well ... it is what it is now 

> Trouble with doing all that stuff with memoryblocks was, though, that I had to write my own methods for base64 decode and quoted-printable decode. Still, it's been fun.

Yeah those were planned to be incorporated but ... as the saying goes .. best laid plans an all that