Dave Storrs <[EMAIL PROTECTED]> writes:
> On Thu, Nov 21, 2002 at 09:43:08PM +, Piers Cawley wrote:
> [ how should printed lists behave? ]
>> Please make the default behaviour 'debugging friendly' rather than
>> 'pretty' if that makes any sense at all. In other words, it'd be handy
>> if whate
At 12:46 PM -0800 11/22/02, Steve Fink wrote:
On Nov-21, Josh Wilmes wrote:
This should correct warnings on a few compilers and outright
breakage on tcc.
It uses the D2FPTR/F2DPTR macros to cast between data and function pointers
where needed.
--Josh
I don't have time to properly test it
On Nov-21, Josh Wilmes wrote:
>
> This should correct warnings on a few compilers and outright breakage on tcc.
>
> It uses the D2FPTR/F2DPTR macros to cast between data and function pointers
> where needed.
>
> --Josh
I don't have time to properly test it right now, but here's an updated
versi
On Fri, Nov 22, 2002 at 12:10:11PM -0800, Michael Lazzaro wrote:
> On Friday, November 22, 2002, at 10:59 AM, Luke Palmer wrote:
> >> From: Michael Lazzaro <[EMAIL PROTECTED]>
> I've been under the impression that the following would _not_ work:
>
> $s ~~ //;
> print "I found $number";
On Friday, November 22, 2002, at 10:59 AM, Luke Palmer wrote:
From: Michael Lazzaro <[EMAIL PROTECTED]>
(This is a bit off-topic, but it's a tiny bit sad that you can name
subrules, but you can't refer to them by name in the interpolation
unless you use hypothetical vars. Eh, no biggie: it would
> Date: Fri, 22 Nov 2002 10:49:08 -0800
> From: Michael Lazzaro <[EMAIL PROTECTED]>
>
> Or, using hypothetical vars:
>
> $s ~~ s/ $num := /$num.as(MoneyFormat)/;
>
> (This is a bit off-topic, but it's a tiny bit sad that you can name
> subrules, but you can't refer to them by name in the i
On Thursday, November 21, 2002, at 11:22 AM, Tanton Gibbs wrote:
It would be very useful in the second half of a s///, too (grab a
match, rewrite it in a canonical form):
$s ~~ s///;
once again, I think it could just be
$s ~~ s//$1.as(MoneyFormat)/
Or, using hypothetical vars:
On Friday, November 22, 2002, at 03:31 AM, Anton Berezin wrote:
This:
- radix > 36, only colon form is allowed, not alpha digits
implies that this:
256#0_253_254_255 # base 256, NOT identical!
is actually not allowed, no?
Ick, good point. In theory, the second of those was suppose
Jason Gloudon wrote:
On Fri, Nov 22, 2002 at 02:04:20PM +0100, Leopold Toetsch wrote:
Parrot_sub_i_i {
Parrot_binop_x_x s//sub/ s/<_N>//
}
The only question I have is .. How am I supposed to read/translate the above ?
Sorry, thought this is obvious ;-)
Parrot_binop_x_x has the body of
# New Ticket Created by Josh Wilmes
# Please include the string: [perl #18600]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=18600 >
[resubmitting properly- sorry, forgot about bugs-parrot]
This should correct warnings on
On Thursday, November 21, 2002, at 04:41 PM, Andrew Wilson wrote:
On Thu, Nov 21, 2002 at 01:02:57PM -0800, Michael Lazzaro wrote:
_01.23 # wrong
01.23_ # wrong
Is _ not space eater, or was that not decided? If it is then aren't
these two just literals with space eaters.
Y
At 3:38 PM -0600 11/15/02, Garrett Goebel wrote:
While I'm here... Will there be a distinction between lists and arrays as
their implemented in Parrot?
Yes.
--
Dan
--"it's like this"---
Dan Sugalski
At 5:11 PM -0500 11/16/02, Erik Lechak wrote:
Hello all,
I have been away for a while. I started writing my own version of
parrot (or at least chunks of it) so I can get a feel for the
current parrot internals. I have learned a lot and now realize why
some things were done the way they were.
On Fri, Nov 22, 2002 at 02:04:20PM +0100, Leopold Toetsch wrote:
> Parrot_sub_i_i {
> Parrot_binop_x_x s//sub/ s/<_N>//
> }
The only question I have is .. How am I supposed to read/translate the above ?
--
Jason
Simon Glover wrote:
On Tue, 19 Nov 2002, Steve Fink wrote:
t/op/lexicals.t 6 1536 66 100.00% 1-6
t/pmc/multiarra 2 512 32 66.67% 2-3
t/pmc/scratchpa 3 768 33 100.00% 1-3
I can get these
On Thu, Nov 21, 2002 at 09:43:08PM +, Piers Cawley wrote:
[ how should printed lists behave? ]
> Please make the default behaviour 'debugging friendly' rather than
> 'pretty' if that makes any sense at all. In other words, it'd be handy
> if whatever got printed out included some unique ID for
Global changes:
* Parrot_jit{_load,_save}_registers have moved to jit.c
- i386, alpha, ppc are adjusted to use the Parrot_jit_emit_mov_* functions
- arm and sun needs still an implementaion for this
* jit2h.pl, i386/core.jit
- function templates:
TEMPLATE Parrot_binop_x_x {
if (MAP[1] && MAP
17 matches
Mail list logo
