Here's a list of the string transformation stuff I think we need:
upcase downcase swapcase upcase first letter downcase first letter
And yes, I know these are meaningless for a good chunk of the encoded data, but that's fine. If there are reasonable text transforms for non-latin alphabets we can see about getting those in. If there's a reason that the sequence "downcase/upcase first" is insufficient to turn a string lower-case except for the first character someone speak up and we'll add in a specialty entry for that.
As for formatting, I think we can reasonably provide both sprintf-style formatting and more traditional COBOL-style formatting. (Which, yes, I know, is generally viewed as nasty, but being able to throw an integer into a "$(999,990.00)" format and get a nicely done money display is really handy) I'm not, however, sure whether it's worth making an op for one or both of these, or throwing them into the standard library. (I can see a good case for building the standard library into the Parrot executable as well, though I'm not sure I want to do that as it'll make it tough to upgrade)
So, anyway, opinions?
--
Dan--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
