[interfacekit] Re: more questions about BString

> I don't know what the performance (or usability) ramifications might be, 
> but when I read this, it immediately occured to me that in python, 
> negative offsets have well-defined semantics that are quite useful.  In 
> IFind(), for instance, using -4 as the offset would initiate the find 
> from whatever the fourth-from-last character/byte is.  Depending on what 
> the issues are, it might be more useful to properly implement negative 
> offset handling than simply clamping to zero.
> 
> Thoughts?
> 
> e

I can see how that might be useful.  The end user can already get this
behavior by adding about 9+(the identifier length) characters to their
program.  Since Length() is inline, I suppose it would be just about as
efficient for the user to do the computation as for BString to do it.  I
would favor moving a change such as this to R2, where we will also
hopefully have a string class that properly handles UTF8. :-)

Andrew

Other related posts: