it is not uncommon to be able to ask a function (in languages of interest to
parrot) to ask whether it takes a variable number of arguments, i.e. it has
a slurpy parameter.
I think it'd be useful to have such a method on the sub pmc, for instance
"is_vararg()".
Whether it should only check for a :
Klaas-Jan Stol wrote:
maybe it'd be useful to allow introspection for that as well? maybe a sub
can be requested for i ts complete signature, which then returns a some
object describing that signature. (how many params, is it a vararg function,
how many optionals, etc)
Writing a method to re
perl -V yields
Summary of my perl5 (revision 5 version 8 subversion 8) configuration:
Platform:
osname=darwin, osvers=9.0, archname=darwin-thread-multi-2level
uname='darwin omen.apple.com 9.0 darwin kernel version 9.0.0b5:
mon sep 10 17:17:11 pdt 2007; root:xnu-1166.6~1release_ppc pow
# New Ticket Created by Bruno
# Please include the string: [perl #49023]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49023 >
---
osname= linux
osvers= 2.6.15.7
arch= i486-linux-gnu-thread-multi
cc= cc
---
Flags:
From: [EMAIL PROTECTED]
Date: Thu, 20 Dec 2007 00:53:12 -0800 (PST)
Author: allison
Date: Thu Dec 20 00:53:11 2007
New Revision: 24108
Added:
trunk/docs/pdds/pdd27_multiple_dispatch.pod
. . .
[pdd] Launch the Multiple Dispatch PDD.
I notice that this doesn't allow
# New Ticket Created by James Keenan
# Please include the string: [perl #49031]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49031 >
The patch attached refactors config/auto/warnings.pm, renames one
test file and provid
The patch attached proposes a refactoring of Parrot configuration step
auto::alignptrs to make it more testable. The patch also revises one
currently existing test file and adds two new test files.
As I've done with other configuration steps and their tests, the focus
of the refactoring has been
