netmaestro wrote:Seriously, it looks like yes? It's no. No, pointers to binary data only, size determined by keysize for the key and MemorySize for the buffers. Where you're getting this utf8 stuff is a mystery. Do you see string types somewhere in the AES command prototypes? If you have difficulty determining buffer size for stringbytelength reasons or for any other reason, trust me the AES library doesn't know a thing about it. Such considerations are for the coder to solve in advance, not the cipher library. It knows pointers and lengths and nothing more. Again, no-strings-in-or-out. Nostrings. InorOut. Give me a tune and I'll sing it to you. But I won't dance. No way. You have to draw the line somewhere.
I know what you talking about, but you should better read before writing so much.
He asked about how AESEncoder() and other functions will read regular PB string, and they are reading it's content as Unicode, because built-in strings using Unicode format. If don't know about that, easily can think than "S$ = PeekS (#PB_UTF8)" will lead S$ to be UTF8 internally.