Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
P6Invocation should act more like a mutable iterator; we'll only clon…
…e it if we have to.
  • Loading branch information
jnthn committed May 6, 2009
1 parent bd1c1e9 commit 2e2f74b
Showing 1 changed file with 1 addition and 4 deletions.
5 changes: 1 addition & 4 deletions src/pmc/p6invocation.pmc
Expand Up @@ -25,7 +25,7 @@ gets stuck into the lex pad to represent the the candidate list.
static PMC *get_next_candidate(PARROT_INTERP, PMC *SELF) {
PMC *candidates, *current;
INTVAL position;

/* Get candidates and position. */
GETATTR_P6Invocation_candidate_list(interp, SELF, candidates);
GETATTR_P6Invocation_position(interp, SELF, position);
Expand Down Expand Up @@ -98,9 +98,6 @@ pmclass P6Invocation need_ext dynpmc group perl6_group {
PMC *lexpad, *first_candidate;
opcode_t *addr;

/* We always operate on a clone of ourself. */
SELF = VTABLE_clone(interp, SELF);

/* In the straightforward case, we know our first candidate right off the
* bat; if not, use list. We also nullify first candidate so we hit the
* candidate list next time we're used. */
Expand Down

0 comments on commit 2e2f74b

Please sign in to comment.