Sam Ruby <[EMAIL PROTECTED]> wrote:
> How about:
>METHOD INTVAL find(PMC* substr) {
Sure, we need a return value ;)
> Patch attached. Should the Object parameter be named "pmc" or "self"?
Great. I'd say for consistency "pmc".
> - Sam Ruby
Thanks, applied.
leo
# New Ticket Created by Sam Ruby
# Please include the string: [perl #31975]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=31975 >
Leopold Toetsch wrote:
> Sam Ruby <[EMAIL PROTECTED]> wrote:
>
>>I'm not overly concern
Sam Ruby <[EMAIL PROTECTED]> wrote:
> What I found was that I could add a regular method, but __init methods
> won't get called.
It's C<__init__> with the --python switch. But both aren't called
for plain PMCs, only for objects.
> However, any subclasses will be aware of both the
> __init and re
I know that there is no reason why this shouldn't work, but I tried it
anyway: I tried adding methods to existing (builtin) PMCs. In this
case, I added a "find" method to a PyString (a near clone of PerlString).
What I found was that I could add a regular method, but __init methods
won't get c
