Allison Randal wrote in perl.perl6.internals :
> In the Python test suite, there's a single global location to declare a
> list of test files that are expected to be skipped on a particular
> platform. This has a much cleaner feel than our own motley collection of
> skip and todo markers in vari
David Fetter wrote in perl.perl6.internals :
> Folks,
>
> I've been wrestling with the .spec file to generate RPMs for parrot
> 0.4.12, and so far, the .spec file is winning, so I figured I'd do
> what I always do when I'm losing: fight dirty and call in help :)
I think that Steven Pritchard has w
Larry Wall wrote in perl.perl6.internals :
> Do bear in mind that Perl can execute bits of code as it's compiling,
> so if a bit of code is untrustworthy, you shouldn't be compiling it
> in the first place, unless you've prescanned it to reject C,
> C, and other macro definitions, or (more usefully
Dan Sugalski wrote in perl.perl6.internals :
> At 2:50 PM +0100 3/24/04, Leopold Toetsch wrote:
>>Dan Sugalski <[EMAIL PROTECTED]> wrote:
>>
>>> At any rate, perl 5's Safe module is a good example of the Wrong Way
>>> to do security, and as such we're going to take it as a cautionary
>>> tale ra
Dan Sugalski wrote in perl.perl6.internals :
>
> This seems... too simple, so I'm sure I'm missing something besides
> the potential massive memory usage. So, by all means, have at it.
You'll need to worry about actions that invalidate all or part of the
method cache : introduction of a new clas
Larry Wall wrote in perl.perl6.internals :
>
> Not using metaconfig (or something like it) would be the biggest
> mistake. It's actually next to impossible to maintain something like
> a Configure script directly.
Actually as parrot already uses IIUC variables set up by Configure,
I think one co
Jerome Quelin wrote in perl.perl6.internals :
>
> But what should those addresses do when receiving a message?
> - parrotbug: should open a RT ticket?
> - status-ok: ?
> - status-nok: should open a RT ticket?
Excuse me from stepping in, but I don't see why three adresses are
necessary. From my (l
Piers Cawley wrote in perl.perl6.internals :
> I want a Ponie!
> I promise that, as development of Ponie (the port of Perl 5 to Parrot)
> accelerates you'll see a summary of Ponie activity in this summary as
> well.
In fact I imagined I was more or less going to do this, based on
imagi
Robert Spier wrote in perl.perl6.internals :
>
> A lot of projects have a "HACKING" file that explains "ground rules"
> for contributing to the project -- all in one place. (Or at least it
> references where things are.)
I'd love to see a file like this in parrot.
Perl 5 provides pod/perlhack.po
Alan Burlison wrote in perl.perl6.internals :
> Piers Cawley wrote:
>
>> Small Perl task for the interested
>> Want to get involved in the Parrot development process? Don't know much
>> about Virtual Machine design and implementation? Do know Perl? Dan has a
>> small but interesting
Nicholas Clark wrote in perl.perl6.internals :
>
>> > r->score = r->use_count + (r->lhs_use_count << 2);
>> >
>> >r->score += 1 << (loop_depth * 3);
[...]
> I wonder how hard it would be to make a --fsummon-nasal-demons flag for gcc
> that added trap code for all classes of undefined behavi
Dan Sugalski wrote in perl.perl6.internals :
>
> In Perl terms, assume we have a method PRE that gets called before
> any method in a class is called, and AUTOLOAD which is called if you
> call a method on a class and that method doesn't exist. Does AUTOLOAD
> have to get called to check for PR
Dan Sugalski wrote in perl.perl6.internals :
> Okay, here are some tasks for the interested. They're all related (I
> expect you'll see the pattern), but independent anyway.
>
> 1) Dig through the perl source and find out all the opcodes. (pp.c
> and friends) Document the opcodes and what they
Melvin Smith wrote in perl.perl6.internals :
>
> It sounds like what you are embarking on is a compiler implementation
> with a full grammar, etc. Right?
Not at all, he wants to reuse the perl 5 parser to generate parrot
opcodes from perl 5 opcodes.
> I also remember there was work already in p
forget to test it with and without threads. Look at the
existing B:: modules for hints.
--
Rafael Garcia-Suarez : http://rgarciasuarez.free.fr/
It's not a can of worms, it's a tank of shai-hulud.
-- Jarkko Hietaniemi
Simon Cozens wrote in perl.perl6.internals:
>
> Similarly, I'd like Parrot/ to move to lib/
And Test/, while you're at it.
> But doesn't this require much CVS hackery to keep the revision history?
Don't be the slave of your tools ;-)
--
Rafael Garcia-Suarez
16 matches
Mail list logo
