On Wed, Aug 10, 2005 at 02:56:46PM +0200, Leopold Toetsch wrote:
> Nicholas Clark via RT wrote:
>
> >I thought that one thing Jarkko learned from perl 5's Unicode model was
> >that
> >the amount of code and pain to support a variable length encoding was
> >greater than the space saving that that
Nicholas Clark via RT wrote:
I thought that one thing Jarkko learned from perl 5's Unicode model was that
the amount of code and pain to support a variable length encoding was
greater than the space saving that that encoding gives.
In turn Dan had decided that Parrot should internally unpack to
On Wed, Aug 03, 2005 at 10:44:47PM +0200, Leopold Toetsch wrote:
>
> On Aug 3, 2005, at 20:58, Will Coleda (via RT) wrote:
>
> >
> >causes a segfault in the substr opcode (from tcl's lib/tclconst.pir),
> >and forces a few tcl-unicode escape tests into TODOs.
> >
> >A short PIR test that is equiva
Will Coleda (via RT) wrote:
causes a segfault in the substr opcode (from tcl's lib/tclconst.pir),
and forces a few tcl-unicode escape tests into TODOs.
A short PIR test that is equivalent:
.sub main @MAIN
$S0 = "\\u666"
$I0 = 0x666
$S1 = chr $I0 # works, but substr doesn't l
On Aug 3, 2005, at 2:58 PM, Will Coleda (via RT) wrote:
With r8787, the following tcl code:
puts \u666
causes a segfault in the substr opcode (from tcl's lib/tclconst.pir),
and forces a few tcl-unicode escape tests into TODOs.
Duh, because it's *evil*.
:-)
Josh
On Aug 3, 2005, at 20:58, Will Coleda (via RT) wrote:
causes a segfault in the substr opcode (from tcl's lib/tclconst.pir),
and forces a few tcl-unicode escape tests into TODOs.
A short PIR test that is equivalent:
.sub main @MAIN
$S0 = "\\u666"
$I0 = 0x666
$S1 = chr $I0 # w
# New Ticket Created by Will Coleda
# Please include the string: [perl #36794]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=36794 >
With r8787, the following tcl code:
puts \u666
causes a segfault in the substr opcode
