> I sent a newer patch into bugs-parrot, but it doesn't seem to have
> made it around to this list. Should I
> a) be more patient (not a problem, this is a minor issue), or
> b) resubmit the patch? (to this list or to bugs-parrot?)
Only the _initial_ message sent to bugs-parrot gets sent to the l
Iain Truskett <[EMAIL PROTECTED]> writes:
> * Alberto Manuel Brandão Simões [15 Aug 2003 00:36]:
>> On Thu, 2003-08-14 at 15:19, Iain Truskett wrote:
> [...]
>> > Much like "Perl 6 Essentials" then?
>> >
>> > I must say that its chapter 4 is the clearest look at
>> > the perl 6 syntax (as it was a
--- Sean O'Rourke <[EMAIL PROTECTED]> wrote:
> Luke Palmer <[EMAIL PROTECTED]>
> writes:
>
> > How does one call a parrot Sub from
> > C and get the
>
> I'd vote for stuffing args into the
> interpreter, calling the sub's invoke()
> method, then digging through the registers
> to pull out the ret
Luke Palmer <[EMAIL PROTECTED]> writes:
> How does one call a parrot Sub from C and get the return value(s)?
I'd vote for stuffing args into the interpreter, calling the sub's
invoke() method, then digging through the registers to pull out the
return values (see e.g. Parrot_pop_argv in method_uti
How does one call a parrot Sub from C and get the return value(s)? Is
it even possible, given CPS, to do this generally? If not, how can I
check when it is?
Thanks,
Luke
Kenneth Graves wrote:
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Wed, 13 Aug 2003 12:42:22 +0200
Kenneth Graves <[EMAIL PROTECTED]> wrote:
> +| NEW { /*expect_pasm = 1;*/ }
I'd rather not mess around with PASM mode.
Patch welcome (if that's
Benjamin Goldberg <[EMAIL PROTECTED]> wrote:
> ... I'd rather have two versions of add, one
> with set/create semantics and the other with assign/mutate semantics.
As already outlined, this leads to some kind of duplicating of our
opcodes, vtables, penalty on JIT implementators and so on. We (/me
Togos <[EMAIL PROTECTED]> wrote:
> ... a bit strange that there is a keyed version
> of 'add', anyway.
What is that? I'd tossed all (hopefully) of the math, boolean, and
logical keyed vtables, for which we never want to have opcodes. Did I
miss one?
Ah yes - docu needs updating, but Dan didn't p
On Fri, 15 Aug 15, 2003 Dan Sugalski wrote:
> On Fri, 15 Aug 2003, TOGoS wrote:
>
> > There may be something I'm missing, but I don't
> > understand why we need a keyed version of just
> > about every opcode.
>
> It avoids having to create a lot of temporary PMCs with weird
> magic on them, av
# New Ticket Created by Andy Bussey
# Please include the string: [perl #23334]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=23334 >
Here's a revised patch to add the IMCC tests
to 'make test' and 'make fulltest' - this ti
There are a couple of minor tweaks to qa.perl.org. Soon, I'll have a
page up for the Phalanx project and THEN we'll have ourselves a good
time!
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
On Friday, August 15, 2003, at 06:49 pm, Kurt Starsinic wrote:
[snip]
Worth being familiar with. Very practical. If anybody knows a
good book on Junit (if there is such a thing, HHOS), I would love
to know about it.
"Unit Testing in Java: How Tests Drive the Code" by Johannes Link &
Peter F
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Wed, 13 Aug 2003 12:42:22 +0200
Kenneth Graves <[EMAIL PROTECTED]> wrote:
> +| NEW { /*expect_pasm = 1;*/ }
I'd rather not mess around with PASM mode.
Patch welcome (if that's not possbile, I'll ha
On Aug 15, Adrian Howard wrote:
> Three I would thoroughly recommend, although not Perl related in any
> way, are:
>
> Lessons Learned in Software Testing: a Context-driven Approach
> Cem Kaner, James Bach
> Publisher: John Wiley & Sons Inc; ISBN: 0471081124
>
>
On Fri, Aug 15, 2003 at 09:25:05AM -, Rafael Garcia-Suarez wrote:
> Michael G Schwern wrote in perl.qa :
> > http://www.pobox.com/~schwern/cgi-bin/perl-qa-wiki.cgi
>
> Do you want a link to this from qa.perl.org ?
Sure.
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~s
On Fri, 15 Aug 2003, TOGoS wrote:
> There may be something I'm missing, but I don't
> understand why we need a keyed version of just
> about every opcode.
It avoids having to create a lot of temporary PMCs with weird magic on
them, avoids having to create temporary PMCs in general, and allows t
> Brent Dax wrote:
> > TOGoS:
> > # When I say in IMCC:
> > #
> > # $P0 = $P1 + $P2
> > #
> > # , I expect it to create a new value and
> > # store it in
> > # $P0, not give me a segfault because I didn't say
> > #
> > # $P0 = new > # $P0 is supposed to be based
> > #
In the second chunk of the patch [classes/env.pmc], what is free_it set
to if the else branch is taken? IOW, I think you should have free_it
initialized to 0 when you declare it.
In the last part of the patch [config/gen/platform/win32.c], why do you
set *free_it to 0 even when you return NULL?
Brent Dax wrote:
>
> TOGoS:
> # When I say in IMCC:
> #
> # $P0 = $P1 + $P2
> #
> # , I expect it to create a new value and store it in
> # $P0, not give me a segfault because I didn't say
> #
> # $P0 = new # $P0 is supposed to be based
> # on the types of $P1 and
On Fri, 15 Aug 2003, Leopold Toetsch wrote:
> When we have more classes like a Python hierarchy, we will see, how and
> how far the functionality does match. If we find some, we can put in an
> intermediate ParrotScalar.
I was thinking about this earlier today. Once dynamic
PMCs are working, Perl
If you want to compile your .pbc to $(EXE) but you don't want
blib/lib/libparrot.a included in each one, you can do it by linking the
generated .o with blib/lib/libparrot.so (you can try "make exec_so
EXEC=" but I'm unsure if it will work correctly)
In order to have this working you must recom
Nicholas Clark <[EMAIL PROTECTED]> wrote:
> On Fri, Aug 15, 2003 at 04:22:36PM +0200, Juergen Boemmels wrote:
>> No STDERR should not let the init fail, but might set the handle to
>> PerlUndef. This is possible since the standard handles are PMCs
>
> We keep using that 4 letter word.
> H
Juergen Boemmels <[EMAIL PROTECTED]> wrote:
> Leopold Toetsch <[EMAIL PROTECTED]> writes:
>> Some notes about current PackFile status quo as of patch #8.
>>
>> Short summary:
>> * Parrot can load a compiled bytecode file call a subroutine
>>in there and return back again. s. imcc/t/syn/file.t
--- Bernhard Schmalhofer <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have started an implementation of m4 in PIR. See
> http://www.gnu.org/software/m4/m4.html.
That is amazing!
>
> The goal is to make a lot of tests work, and eventually getting a
> drop
> in replacement for GNU m4.
> The plan is t
I've started a new job this week, and between finishing the last one and
getting this going it's changed my schedule rather a lot. Settling down,
though, so I should be in a position to at least trickle out mail again.
I'll be draining out the queue tonight and tomorrow morning (GMT-500 if
you're
Vladimir Lipskiy <[EMAIL PROTECTED]> wrote:
> I surmise that there is something which set up
> interpreter->has_early_DOD_PMCs = 1
> before the test runs.
Yep, probably the stdio PMCs. These (or better all) are inititalized
currently with:
PObj_needs_early_DOD_SET(pmc);
interpreter->has_earl
Michal Wallace <[EMAIL PROTECTED]> wrote:
> "raise hell" is working great
> with the new find_lex exceptions. Thanks! :)
Welcome, and thanks for using, testing, feddback ...
> Any plans to to add pow for PMC's?
Seems to be missing, ind pdd02 too.
> What about separate ops for floor/true divisi
Leopold Toetsch <[EMAIL PROTECTED]> writes:
> Some notes about current PackFile status quo as of patch #8.
>
> Short summary:
> * Parrot can load a compiled bytecode file call a subroutine
>in there and return back again. s. imcc/t/syn/file.t (#6)
this is cool.
[...]
> Missing:
> * cleanup
On Fri, Aug 15, 2003 at 04:22:36PM +0200, Juergen Boemmels wrote:
> No STDERR should not let the init fail, but might set the handle to
> PerlUndef. This is possible since the standard handles are PMCs
We keep using that 4 letter word.
How much s/Perl/Parrot/ig do we need before the entir
Michael G Schwern wrote:
What books out there are of use for those wanting to learn Perl testing?
They don't necessarily have to be specificly about *Perl* testing.
I've put up a Wiki page to generate a listing.
http://www.pobox.com/~schwern/cgi-bin/perl-qa-wiki.cgi?TestingBooks
That URL is redirec
Leopold Toetsch <[EMAIL PROTECTED]> writes:
> Arthur Bergman <[EMAIL PROTECTED]> wrote:
>
> Hi Arthur,
>
> > Hi,
>
> > If I execute a miniperl (but linked into parrot and with it's own
> > parrot interpreter) it works, but if the caller closes(STDERR) before
> > invoking miniperl no output is e
D:\Perl\5.6.1\bin\MSWin32-x86-multi-thread\perl.exe
t/harness --gc-debug
--running-make-test
t/op/gcNOK 2# Failed test (t/op/gc.t at line 14)
# got: '1'
# expected: '0'
t/op/gcok 8/8# Looks like you failed 1 tests of 8.
t/op/gcdubious
Test returned stat
"raise hell" is working great
with the new find_lex exceptions. Thanks! :)
Any plans to to add pow for PMC's?
What about separate ops for floor/true division?
http://www.python.org/doc/2.2.1/whatsnew/node7.html
Sincerely,
Michal J Wallace
Sabren Enterprises, Inc.
Mattia Barbon <[EMAIL PROTECTED]> wrote:
> Hello,
> the correct fix is probably having different code paths for Win32 (because
> on Windows NT/2000/XP/.Net and funnier names of the future environment
> is/will be Unicode, not char*). For now this makes env.t pass on Win32.
Thanks, applied.
leo
Lars Balker Rasmussen <[EMAIL PROTECTED]> wrote:
> Just to fix some cvs up noise...
Thanks, applied.
leo
Andy Bussey <[EMAIL PROTECTED]> wrote:
> There may be a good reason that I don't know about
> why 'make test' does not run the IMCC tests, but if
> not here's a patch.
No, there is no reason. But could you provide a patch for
config/gen/makefiles/root.in.
> Cheers,
> Andy Bussey
Thanks,
leo
Some notes about current PackFile status quo as of patch #8.
Short summary:
* Parrot can load a compiled bytecode file call a subroutine
in there and return back again. s. imcc/t/syn/file.t (#6)
How it works:
* A subroutine using Parrot Calling Conventions (PCC) has an entry
in the constant ta
On Thursday 14 August 2003 18:24, Mattia Barbon wrote:
> Puts #ifdefs as per the rest of i386/jit_emit.h.
>
> Regards
> Mattia
Applied, Thanks.
Daniel.
Three I would thoroughly recommend, although not Perl related in any
way, are:
Lessons Learned in Software Testing: a Context-driven Approach
Cem Kaner, James Bach
Publisher: John Wiley & Sons Inc; ISBN: 0471081124
Testing Extreme Programming
Michael G Schwern wrote in perl.qa :
> http://www.pobox.com/~schwern/cgi-bin/perl-qa-wiki.cgi
Do you want a link to this from qa.perl.org ?
# New Ticket Created by Lars Balker Rasmussen
# Please include the string: [perl #23326]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=23326 >
Just to fix some cvs up noise...
--
Lars Balker Rasmussen
I'm often embarassed when I get ot the end of a testing tutorial and come
to the section on suggested books which pretty much consists of
"Perl Debugged".
What books out there are of use for those wanting to learn Perl testing?
They don't necessarily have to be specificly about *Perl* testing.
I'
As I've obtained a stable server on which I have root, I've moved the
QA Wiki there so the permissions problems which have plagued it will be
no more!
The existing URL will work fine.
http://www.pobox.com/~schwern/cgi-bin/perl-qa-wiki.cgi
--
Michael G Schwern[EMAIL PROTECTED] http://ww
# New Ticket Created by Andy Bussey
# Please include the string: [perl #23322]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=23322 >
There may be a good reason that I don't know about
why 'make test' does not run the IMCC
44 matches
Mail list logo
