develooper Front page | perl.perl5.porters | Postings from February 2001

Re: IV preservation (was Re: [PATCH 5.7.0] compiling on OS/2)

Thread Previous | Thread Next
From:
Jarkko Hietaniemi
Date:
February 14, 2001 12:27
Subject:
Re: IV preservation (was Re: [PATCH 5.7.0] compiling on OS/2)
Message ID:
20010214142726.H10804@chaos.wustl.edu
> On the scale of disasters in the Perl design, IMO this is less than
> the qu// horror, but on par with forcing h2xs to produce a
> backwards-incompatible code, v3.4.5 thingies, or using REx-opcodes
> which switch their unicode-face at runtime.

I won't comment on the IV/UV matters but on this I feel personally
obliged to say something on these.  Polymorphic REx-opcodes are a necessity
because out data is polymorphic in its Unicodeness, in compile-time
you cannot know what the data will be.  I see no way out of that.

About the proposed qu//: it's not a perfect solution, but it is a
compromise.  It gives for those of who need us the way to produce
UTF-8: compactly and in compile-time, as opposed to pack("U", ...).
Yes, \x{HH} where 0x80 <= HH <= 0xff used to do that, but that lead
into all sorts of irregularities with the rest of language (including
the v-strings), and in EBCDIC lands into even more brain hurt.

> Hope this helps,

No. Not really.  Drive-by-dumping of heaps of negative commentary on
our front lawn with no constructive suggestions at all is not very
helpful.  More professional that "you guys suck" since you did have
technical details and reasoning behind your doubts, but helpful, nah.

> Ilya

-- 
$jhi++; # http://www.iki.fi/jhi/
        # There is this special biologist word we use for 'stable'.
        # It is 'dead'. -- Jack Cohen

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About