Leopold Toetsch wrote:
cvsuser     04/12/11 04:08:13

  Modified:    classes  sub.pmc
               imcc/t/syn op.t
               runtime/parrot/library parrotlib.imc
               src      inter_run.c
               t/op     gc.t
               t/pmc    delegate.t object-meths.t objects.t sub.t
  Log:
  more pdd03 cleanup
  * P0, P2 aren't visible in caller aynmore

This caused a number of Python tests to fail... specifically any tests which were improperly depending on P2 as PDD03 states:


    Note particularly that P0-P2 are not passed.

I'll go back and all the necessary interpinfo calls, but I feel compelled to ask: why isn't P2 passed? It seems to me quite likely that most methods will want to know what object they are working on.

- Sam Ruby
.sub main @MAIN
    newclass $P0, 'c'
    find_type $I0, 'c'
    new $P1, $I0

    new $P2, .PerlInt
    $P2 = 1234
    setprop $P1, 'p', $P2

    $P3 = $P1.m()
    print $P3
    print "\n"
.end

.namespace ['c']
.sub m method
    $P4 = P2
    getprop $P5, 'p', $P4
    .return ($P5)
.end

Reply via email to