I've upgraded the experimental perl.org cvsmonitor implementation.
It's very cool. Take a peek:
http://rt.perl.org/cgi-bin/cvsmonitor/cvsmonitor.pl?cmd=viewModule&module=perl_public.parrot
-or-
http://snipurl.com/9hn
It gets updated once a day, around 3 AM Pacific time, AKA 6 AM Eastern
Time
# New Ticket Created by Jonathan Sillito
# Please include the string: [perl #18170]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=18170 >
The attached patch implements a very complete set of lexical scope
semantics. For th
On Tue, 29 Oct 2002 09:55:23 -0800, Chromatic wrote:
>
>I'd really like to be able to save comments from
>source files as metadata. This has at least two
>potential benefits. First, it >makes it much easier
>to recreate the whole file from bytecode (especially
>refactored bytecode).
>Second, it
# New Ticket Created by Jonathan Sillito
# Please include the string: [perl #18166]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=18166 >
pdd09 mentions routines for blocking and unblocking both GC and DOD, however
I can n
On Wed, 30 Oct 2002, Leopold Toetsch wrote:
> > Nicholas Clark suggested that we could perhaps use a union, something like
>
> Nice idea - works for me (gcc 2.95.2)
>
> Slightly modified - please try this (cc -Wall -Wcast-qual ..)
> static union {
> const void * __c_ptr;
> void * __
Andy Dougherty wrote:
On Wed, 30 Oct 2002, Leopold Toetsch wrote:
[sundry 'const' warnings]
Nicholas Clark suggested that we could perhaps use a union, something like
Nice idea - works for me (gcc 2.95.2)
Slightly modified - please try this (cc -Wall -Wcast-qual ..)
static union {
cons
On Wed, 30 Oct 2002, Leopold Toetsch wrote:
[sundry 'const' warnings]
> This warning WRT (void*) buffer was introduced for tcc, says the
> comment. Can we put a
> #ifdef __tcc__ / #endif around this - does tcc define something like this?
Short answer: Yes, but it wouldn't really make any signf
Peter Gibbs wrote:
Leopold Toetsch wrote:
- insert more const decls (e.g. string_trans_code doesn't modify its
src, so ...
At one stage all the source strings were defined as const; I believe
this changed with the introduction of COW strings. For example,
string_transcode may call string_co
Nicholas Clark wrote:
I'd prefer more real and explicit use of const, and correcting all const-ness
mistakes, rather than leaving it as a hint to the programmer. It's possible
that compilers will be able to optimise better if they know something is
const.
Ack.
Also, no-one commented on my
Peter Gibbs (via RT) wrote:
# New Ticket Created by Peter Gibbs
# Please include the string: [perl #18157]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=18157 >
t/src/sprintf.t test 1 fails due to too many percentage sig
perl6 --test --gc-debug
runs all tests through parrot --gc-debug ... they pass ;-)
leo
Leopold Toetsch wrote:
> - const is currently used in some string.c functions rather inconsistently
> - should we remove it alltogether
> - introduce a dummy CONST define as hint for the programmer
> - insert more const decls (e.g. string_trans_code doesn't modify its
> src, so ...
At one stage al
On Wed, Oct 30, 2002 at 11:13:09AM +0100, Leopold Toetsch wrote:
> I moved the two - almost identical - op bodys out of core.ops
> and called this functions string_str_index...
>
> and did introduce a new warning WRT const.
>
> - const is currently used in some string.c functions rather in
I moved the two - almost identical - op bodys out of core.ops
and called this functions string_str_index...
and did introduce a new warning WRT const.
- const is currently used in some string.c functions rather inconsistently
- should we remove it alltogether
- introduce a dummy CONST defi
# New Ticket Created by Peter Gibbs
# Please include the string: [perl #18157]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=18157 >
t/src/sprintf.t test 1 fails due to too many percentage signs
Patch below seems to fix.
Jason Gloudon wrote:
... By default both compilers align stack variables at their natural
alignment, so PMC pointers would normally fall on 4 byte boundaries.
However, it is also possible that someone might save a PMC pointer to an
unaligned address on the stack (I can't imagine why). We could a
16 matches
Mail list logo