[parrot/parrot] 45d8c8: Not yet functional implementation of proxy pmc

[noreply at github.com]

  Branch: refs/heads/threads
  Home:   https://github.com/parrot/parrot

  Commit: 45d8c8bbf1e4864eea4aa0612781c206eccafb4f
      https://github.com/parrot/parrot/commit/45d8c8bbf1e4864eea4aa0612781c206eccafb4f
  Author: Stefan Seifert <nine at detonation.org>
  Date:   2011-11-13 (Sun, 13 Nov 2011)

  Changed paths:
    M MANIFEST
  A lib/Parrot/Pmc2c/PMC/Proxy.pm
  M lib/Parrot/Pmc2c/Pmc2cMain.pm
  A src/pmc/proxy.pmc
  M src/pmc/task.pmc
  M t/src/threads.t

  Log Message:
  -----------
  Not yet functional implementation of proxy pmc


  Commit: ddf25025eed0bb004a27bf5f4eb5b18abeec49bc
      https://github.com/parrot/parrot/commit/ddf25025eed0bb004a27bf5f4eb5b18abeec49bc
  Author: Stefan Seifert <nine at detonation.org>
  Date:   2011-11-14 (Mon, 14 Nov 2011)

  Changed paths:
    M src/pmc/parrotinterpreter.pmc
  M src/pmc/proxy.pmc
  M src/pmc/task.pmc
  M t/src/threads.t

  Log Message:
  -----------
  Fix scheduling updates on data owning interpreters

Storing references to foreign interpreters and probably other objects as
well screws up garbage collection and leads to all kinds of strange
errors.

Accessing attributes or methods of the proxy pmc itself leads to a whole
lot of confusion about for example which namespace to search.

Working solution is a new schedule_proxied method which keeps access to
the proxy's attributes and the foreign interp in C space where it's
safe.


Compare: https://github.com/parrot/parrot/compare/53d28d8...ddf2502