Will Coleda wrote:
Updating Data::Escape seems like a better option to me.
Done - r8939.
BTW Data/Escape needs tests and it doesn't handle non-ascii chars. I was
also wondering if it could use the *cclass opcodes to advance the string
pos but didn't find docs about available CCLASS constan
Leopold Toetsch wrote:
> ... I was
also wondering if it could use the *cclass opcodes to advance the string
pos but didn't find docs about available CCLASS constants and what they
are matching.
runtime/parrot/include/cclass.pasm has PASM constants for the various
bits and reveals that it is
Below is a list of opcodes that will go away or change soon (unless
someone loudly hollers of course). This list is also available as file
branches/leo-ctx5/DEPRECATED.
leo
Deprecated opcodes (branches/leo-ctx5 first)
findclass(out INT, in STR)
returns a boolean bit if the class exists. The
Leopold Toetsch wrote:
Below is a list of opcodes that will go away or change soon (unless
someone loudly hollers of course). This list is also available as file
branches/leo-ctx5/DEPRECATED.
I have added some more to DEPRECATED, nameley stack calling convention
directives .param, .arg, .re
# New Ticket Created by Curtis Rawls
# Please include the string: [perl #36892]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=36892 >
-Rewrites optimization loop to iterate through all optimizations optimally
-Makes pre_o
On Sat, 2005-08-13 at 15:22 +0200, Leopold Toetsch wrote:
> I have added some more to DEPRECATED, nameley stack calling convention
> directives .param, .arg, .return, .result, which just translate to user
> stack opcodes 'save' or 'restore' and 'call'.
Can you give an example of translating cod
On Tue, Jun 14, 2005 at 07:56:32PM +0200, Ingo Blechschmidt wrote:
> Maybe we should just hardcode the filehandles-leaking-into-runtime case
> in the compiler? And, if the compiler can't detect the problem at
> compile-time, just throw a runtime exception?
>
> my $fh = BEGIN { open "some_file"
Hi,
Nicholas Clark wrote:
> On Tue, Jun 14, 2005 at 07:56:32PM +0200, Ingo Blechschmidt wrote:
>> Maybe we should just hardcode the filehandles-leaking-into-runtime
>> case in the compiler? And, if the compiler can't detect the problem
>> at compile-time, just throw a runtime exception?
>>
>>
