DBCS versus skip_backward

Whilst attempting to implement DBCS encoding, I have discovered that skip_backward cannot be implemented for this encoding style, due to the mixture of 1-byte and 2-byte characters. Some of the available options: 1) Throw an exception if somebody tries to skip_backward in a DBCS string 2)

[perl #24391] [PATCH] P6C closures use 'newsub' instead of assigning integer address

# New Ticket Created by Allison Randal # Please include the string: [perl #24391] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt2/Ticket/Display.html?id=24391 Several tests in t/compiler/call.t were failing with the error:

[perl #24392] [PATCH] P6C xor really does return a value

# New Ticket Created by Allison Randal # Please include the string: [perl #24392] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt2/Ticket/Display.html?id=24392 This patch changes the test instead of the code. The code is actually correct.

Strings PDD

In an attempt to understand what the plan is with regard to ICU and Parrot strings in general, I've been gathering together links to previous bits of discussion on: http://www.vendian.org/parrot/wiki/bin/view.cgi/Main/ ParrotDistributionUnicodeSupport Obviously what is still needed is

[perl #24396] FAIL parrot-0.0.13 MSWin32-x86-multi-thread

# New Ticket Created by [EMAIL PROTECTED] # Please include the string: [perl #24396] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt2/Ticket/Display.html?id=24396 ... t\src\io..NOK 9# Failed test (t\src\io.t at line 242) #

Re: [perl #24391] [PATCH] P6C closures use 'newsub' instead of assigning integer address

thanks, applied. /s

Re: [perl #24392] [PATCH] P6C xor really does return a value

applied thanks. /s

docs

Hello. I have several questions about parrot dosc. I have noticed that docs\parrot_assembly.pod is old version of \docs\pdds\pdd06_pasm.pod file. Will these files be distinguished in the future? Catalog docs\ops is empty in 0.0.13 version. Is it bug? Nick.

Re: docs

On Mon, 3 Nov 2003, Nick Kostirya wrote: Hello. I have several questions about parrot dosc. I have noticed that docs\parrot_assembly.pod is old version of \docs\pdds\pdd06_pasm.pod file. Will these files be distinguished in the future? And they're both wrong, unfortunately. :( pdd06 is

Re: [perl #24257] [PATCH] Integration of ICU to the build system

Jürgen Bömmels (via RT) [EMAIL PROTECTED] writes: The attached patch makes it an optional part of the normal build system. By using the switch --buildicu the ./configure of icu/source is run and the makefile is extended with rules for building and cleaning icu. This option is not enabled by

Re: docs

On Mon, 3 Nov 2003, Dan Sugalski wrote: On Mon, 3 Nov 2003, Nick Kostirya wrote: Catalog docs\ops is empty in 0.0.13 version. Is it bug? I think that's leftover cruft. Well, we used to generate a .pod file for each .ops file, at build time, which lived in here. However, we don't

From the Interesting, but is it useful? department

I've been playing with an uncommitted op version of invoke that takes a method or sub by name like below: invoke foo, 0 The 0 is irrelevant to the eye, but it is a placeholder for the self-modifying instruction. Upon call, invoke by name does: op invoke(STR, INT) PMC sub if($2 == 0) { sub =

Re: docs

Simon Glover [EMAIL PROTECTED] writes: On Mon, 3 Nov 2003, Dan Sugalski wrote: On Mon, 3 Nov 2003, Nick Kostirya wrote: Catalog docs\ops is empty in 0.0.13 version. Is it bug? I think that's leftover cruft. Well, we used to generate a .pod file for each .ops file, at build