Simon Cozens <[EMAIL PROTECTED]>
> IMHO, the first thing we need to design and code is the API and runtime
> library, since everything else builds on top of that, and we can design other
> stuff in parallel with coding it. (A lot of it will be grunt work.)
Personally I feel that that string part of the SV API should include most
(if not all) string functions, including regex matching and substitution.
That way way there can be multiple regex implementations to handle different
cases (eg fast one(s) for fixed width ASCII, UTF-32 etc, and a slow horrible one
for variable-length UTF-8, etc). Of course perl itself could provide a default regex
engine usable by all string types, but implementors would then be free to add
variants for custom string types.
If *all* strings ops apart from initial assignment and final export are internal
to the SV type, this should make life a lot easier for everyone (apart from
the person who has to implement the type ;-)
