On Feb 12, 2006, at 2:27, Jonathan Worthington wrote:
This problem would go away if I had a way of doing a find_global or
findmethod but also specifying the types that make up the signature.
The sequence of:
set_args '(...)', ...
f = find_name 'func'
should exactly do, what you need.
On Feb 12, 2006, at 3:07, Jonathan Worthington wrote:
The usage of the C<.namespace> directive causes the creation of a new
namespace PMC with that name. Additionally the namespace PMC is
registered
as a type. This needs a bit of additional code that prevents
instantiation
of namespaces.
Ho
On Feb 12, 2006, at 5:30, Bob Rogers wrote:
parrot: src/inter_call.c:899: process_args: Assertion `idx >= 0'
failed.
The backtrace shows argument passing to an exception handler and it
looks like the same bug that made tcl's cmd_global_2 failing.
The 'idx := -1' indicates that there is sti
"Sisyphus" <[EMAIL PROTECTED]> wrote:
My first post here. First up, is there a better place to ask questions
relating to the building of parrot ? If so ... where ? If not ... read
on.
Welcome to the list and yes, you're in the right place. :-)
I'm on Windows 2000, and parrot-0.4.1 builds
"Leopold Toetsch" <[EMAIL PROTECTED]> wrote:
On Feb 12, 2006, at 2:27, Jonathan Worthington wrote:
This problem would go away if I had a way of doing a find_global or
findmethod but also specifying the types that make up the signature.
The sequence of:
set_args '(...)', ...
f = find_n
Jonathan Worthington wrote:
and I'm trying to find a sub/method by knowing the types but not having
arguments that would be seen as that type (e.g. null won't ever be seen
as a particular type). So I think this doesn't really help.
Well, you could use the 'long names' of the multi subs direc
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Sun, 12 Feb 2006 11:51:35 +0100
On Feb 12, 2006, at 5:30, Bob Rogers wrote:
> parrot: src/inter_call.c:899: process_args: Assertion `idx >= 0'
> failed.
The backtrace shows argument passing to an exception handler and it
look
Stevan Little wrote:
> ^Dog is an instance of the MetaClass, while Dog (no ^ sigil) is the
> "class" (actually it's a prototypical instance of the class which the
> metaclass ^Dog describes, but you dont really need to know that to use
> it).
>
> ^Dog.can(bark) # false
> Dog.can(bark) # true
I wrote up a quick patch to os.pmc to add an ls method. Pass it a
directory name, and it'll return a resizablestringarray with the
contents of the directory. But, I don't know anything about the
windows API and can't test it, etc... I don't think there's been any
decision yet on the interfac
Leo, should I apply it for OS or File, or none?
Cheers
Alberto
Joshua Isom wrote:
I wrote up a quick patch to os.pmc to add an ls method. Pass it a
directory name, and it'll return a resizablestringarray with the
contents of the directory. But, I don't know anything about the windows
API an
Thomas Sandlass wrote:
> > > or maybe
> > >
> > > method Dog.bark () { ... }
> >
> > Yes that works too.
>
> Shouldn't that read Dog::bark? Why the dot?
Because I'm not 100% with the proper syntax of things. The intent was
to add a bark() method to Dog during runtime.
--
Jonathan "Dataweaver"
Applied as r11511 (wow, a palindrome revision :-))
Thanks.
Alberto
Joshua Isom wrote:
I wrote up a quick patch to os.pmc to add an ls method. Pass it a
directory name, and it'll return a resizablestringarray with the
contents of the directory. But, I don't know anything about the windows
AP
About a month ago I wrote a example configuration step to show off the
new capability of passing arguments to a step from Configure.pl. It
seems that I forgot to send out an e-mail about this...
The example step is called gen:PodTex and creates plain text files from
Pod documents with Pod::Text.
On Feb 12, 2006, at 21:13, Alberto Simões wrote:
Applied as r11511 (wow, a palindrome revision :-))
And reverted in r11512 by ambs. The choosen method name isn't, well,
the best choice, the used OS calls (opendir/readdir/closedir) should
better be exposed as is, and it didn't compile, becau
I think there's a typo in synopsis 5, "Indirectly quantified subpattern
captures:"
[ (\w+) \: (\w+ \h+)* \n ]**{2...}
I have a feeling the \h should be *, not +.
On Mon, Feb 13, 2006 at 12:23:33AM +0100, Leopold Toetsch wrote:
>
> On Feb 12, 2006, at 21:13, Alberto Sim?es wrote:
>
> >Applied as r11511 (wow, a palindrome revision :-))
>
> And reverted in r11512 by ambs. The choosen method name isn't, well,
> the best choice, the used OS calls (opendir/re
For perl 6,
Array and Scalar are in different namespace.
So,
class A { has $.a; has @.a };
what will A.new.a return by default?
An Error? or Scalar has a higher priority?
Thanks,
xinming
On Sunday 12 February 2006 17:11, Yiyi Hu wrote:
> For perl 6,
> Array and Scalar are in different namespace.
> So,
> class A { has $.a; has @.a };
>
> what will A.new.a return by default?
>
> An Error? or Scalar has a higher priority?
Seems like a compile-time warning (at least) to me.
-- c
The last 2 messages I got from p6l were duplicated, the ones from
Yiyi and chromatic, but the message is only addressed to the list
once, and not addressed to any other recipients. The problem seems
server side, as both my email box and the archive at
http://nntp.perl.org/group/perl.perl6.lang
19 matches
Mail list logo
