Thanks, Jarrko.
On Thursday 17 January 2002 23:21, Jarkko Hietaniemi wrote:
> The most important message is that give up on 8-bit bytes, already.
> Time to move on, chop chop.
Do you think/feel/wish/demand that the textual (string) APIs should differ
from the binary (byte) APIs? (Both from an internal Parrot perspective and
at the language level.)
This may be beyond the scope of the document, but do you have an opinion on
whether strings need to be entirely encapsulated within a single structure,
or whether "virtual" strings (comprising several disparate substrings) are a
viable addition?
typedef struct {
UINTVAL size;
UINTVAL index;
UINTVAL index_offset;
UINTVAL last_offset;
UINTVAL size_valid:1;
UINTVAL offset_valid:1;
UINTVAL last_valid:1;
UINTVAL continued:1;
PARROT_STRING string;
PARROT_SIZED_STRING string_continued;
} PARROT_SIZED_STRING
This was discussed earlier mostly for alleviating some of the headaches
associated with variable-width encodings.
--
Bryan C. Warnock
[EMAIL PROTECTED]
