PeekS() with #PB_Ascii flag in >=PB5.51

[Psychophanta]

Hi all,

since in PB >= 5.51 there is not possible to manage string variables as extended ascii format; what is the meaning of the function PeekS() used with the #PB_Ascii flag ?

[skywalk]

We need this to scan memory that contains Ascii text, even though it is returned into a PB unicode string.

[Psychophanta]

Aha, that's it, and how do you scan a thing if the function does not say that it matches an ascii sequence?

[Sicro]

how do you scan a thing if the function does not say that it matches an ascii sequence?

You can try reading the memory by using different string formats, and the string format that not results in garbage, is the right string format. Sure, this way is very bad.
The only right way is that the developer of the function documents the string format, that the function returns.

[walbus]

Ascii strings have never zero bytes inside
Ascii chars inside a Unicode strings have ever double zero pairs inside, for each character a pair

A PB based Ascii string ends with a zero byte
A PB based Unicode string ends with two zero bytes
This zero bytes are the string termination
Fixed strings (with a defined length) have not a termination

Saved text should have ever a BOM - Looking therefore in the Wikipedia and the PB Doku

Looking also for UTF-8