On 11 Oct 2007, at 11:46, A. Pagaltzis wrote:
* Andy Armstrong <[EMAIL PROTECTED]> [2007-10-10 22:45]:
Nice email address. :-P
It had to be done :)
This evening I started playing with String::Smart (the name is
as provisional as everything else).
Something with “language”, “type”, “quoting” or “escaping” would
be more appropriate I think.
Yup, OK.
In general a String::Smart string knows which transformations
are currently applied to a string and when you ask for a
particular representation of that string it computes the path
from the current encoding to the desired encoding and applies
the transformations in the appropriate order.
Have you seen Tom Moertel’s article on applying Haskell to this?
http://blog.moertel.com/articles/2006/10/18/a-type-based-solution-
to-the-strings-problem
Oh that's nice! Thanks for that.
See also String::EscapeCage, which was discussed recently on this
list, and which is just as horribly named. :-) It differs in
that it doesn’t address the chaining you mention, and by hooking
itself into tainting.
Yeah - it has slightly different aims as far as I can tell.
And I’m almost positive that I have seen one more module that
tries to address the exact same issue.
I assumed there must be one but couldn't find it. Anyone?
--
Andy Armstrong, Hexten
