On Thu, 2004-04-15 at 05:00, Leopold Toetsch wrote:
> Aaron Sherman <[EMAIL PROTECTED]> wrote:
>
> > So, why is that:
>
> > "my dog Fiffi":language("blah") eq "my dog Fi\x{fb03}":langauge("blah")
>
> > and not
>
> > use language "blah";
> > "my dog Fiffi" eq "my dog Fi\x{fb03}"
>
> What, if this is:
>
> $dog eq "my dog Fi\x{fb03}"
>
> and C<$dog> hasn't some language info attached?
Looks good to me. Great example!
Seriously, why is that a problem? That was my entry-point to this
conversation: I just don't see any case in which performing a comparison
of ANY two strings according to whatever arbitrary SINGLE language rules
is a problem. I cannot imagine the case where you need two or more
language rules AND could start off with any sense of what that would
mean, and even if you could contrive such a case, I would suggest that
its rarity should dictate it being attached to a class that defines a
string-like object which mutates its behavior based on the language
spoken by the maintainer of the database from which it was fetched or
somesuch.
--
Aaron Sherman <[EMAIL PROTECTED]>
Senior Systems Engineer and Toolsmith
"It's the sound of a satellite saying, 'get me down!'" -Shriekback
