[parrot/parrot] 3936b5: [pmc] file: UNUSED SELF [cage]

[GitHub]

  Branch: refs/heads/rurban/coros-gh564
  Home:   https://github.com/parrot/parrot
  Commit: 3936b500abdea3691855c9391720d005471b6eb7
      https://github.com/parrot/parrot/commit/3936b500abdea3691855c9391720d005471b6eb7
  Author: Reini Urban <rurban at cpanel.net>
  Date:   2014-10-16 (Thu, 16 Oct 2014)

  Changed paths:
    M src/dynpmc/file.pmc

  Log Message:
  -----------
  [pmc] file: UNUSED SELF [cage]


  Commit: 6243bf6cc9823b668d3c0a11b7cd50b46e8dfe4c
      https://github.com/parrot/parrot/commit/6243bf6cc9823b668d3c0a11b7cd50b46e8dfe4c
  Author: Reini Urban <rurban at cpanel.net>
  Date:   2014-10-16 (Thu, 16 Oct 2014)

  Changed paths:
    M docs/book/pir/ch06_subroutines.pod
    M docs/pmc/subs.pod
    M src/pmc/coroutine.pmc
    M t/pmc/coroutine.t

  Log Message:
  -----------
  [pmc] Clarify dead coroutines

Coros are not resumable when all yield states are exhausted.
This is consistent with the LUA design, which we follow, and all other
coro implementations I know of. Just the parrot book argues that after a
return the state should be automatically reset. Technically no problem, even
without the quirks described in https://github.com/parrot/parrot/issues/564#issuecomment-3503597
or via a seperate reset() method, but semantically an auto-reset is problematic.

Added testcases for all the relevant tickets: #564, #585 and there is on
bug remaining: TT #1003 leading to Null PMC access in get_string on a dead coro


  Commit: 01353b9ef332a513370fae25c14f522a08818fff
      https://github.com/parrot/parrot/commit/01353b9ef332a513370fae25c14f522a08818fff
  Author: Reini Urban <rurban at cpanel.net>
  Date:   2014-10-16 (Thu, 16 Oct 2014)

  Changed paths:
    M config/gen/makefiles/root.in
    M src/ops/core.ops
    M src/ops/core_ops.c
    M src/pmc/coroutine.pmc
    M src/sub.c

  Log Message:
  -----------
  [pmc] Coroutine is now auto-resetting


  Commit: 22e7baa504add677291aea15b2367e5a5c587551
      https://github.com/parrot/parrot/commit/22e7baa504add677291aea15b2367e5a5c587551
  Author: Reini Urban <rurban at cpanel.net>
  Date:   2014-10-16 (Thu, 16 Oct 2014)

  Changed paths:
    M docs/pmc/subs.pod
    M src/pmc/coroutine.pmc
    M t/pmc/coroutine.t

  Log Message:
  -----------
  [pmc] Add Coroutine.reset() method

Mentioned in GH #564.

It is however more efficient to clone an initial coro and
copy this saved clone back, as the context does not need to
be recreated afresh.


  Commit: 69363c8a9dd220f523cc6317dcf1977f25114371
      https://github.com/parrot/parrot/commit/69363c8a9dd220f523cc6317dcf1977f25114371
  Author: Reini Urban <rurban at cpanel.net>
  Date:   2014-10-16 (Thu, 16 Oct 2014)

  Changed paths:
    M src/pmc/coroutine.pmc
    M src/sub.c

  Log Message:
  -----------
  coro: implemented autoreset method and attribute

Still using traceflag 8. Maybe I should adopt it or resuse the SUB_CALL_FLAG?


  Commit: 989a587aec77f92e80715ab84de2a080b1198bb1
      https://github.com/parrot/parrot/commit/989a587aec77f92e80715ab84de2a080b1198bb1
  Author: Reini Urban <rurban at cpanel.net>
  Date:   2014-10-16 (Thu, 16 Oct 2014)

  Changed paths:
    M ChangeLog
    M include/parrot/interpreter.h
    M src/pmc/coroutine.pmc
    M src/sub.c
    M t/pmc/coroutine.t

  Log Message:
  -----------
  core: autoreset tests, TRACE_CORO, PARROT_TRACE_CORO_STATE_FLAG

add TRACE_CORO define, -t8 only usable when not --optimizing
fix -t2 returning from coroutine msg.
-t2 msg either Coroutine autoreset or Coroutine no autoreset
add autoreset test, not yet working (one-off same as TT #1003)


  Commit: 78dcd9af7c28c8bdf68f141282bce44774c44fb4
      https://github.com/parrot/parrot/commit/78dcd9af7c28c8bdf68f141282bce44774c44fb4
  Author: Reini Urban <rurban at cpanel.net>
  Date:   2014-10-16 (Thu, 16 Oct 2014)

  Changed paths:
    M ChangeLog
    M frontend/parrot/main.c
    M frontend/parrot2/main.c
    M frontend/parrot2/prt0.pir
    M frontend/parrot2/prt0.winxed

  Log Message:
  -----------
  Document -t8 flag, harmonize parrot usage messages

along parrot and parrot_old
Omit GH issue prefix from ChangeLog if default.


Compare: https://github.com/parrot/parrot/compare/5011c55de74a...78dcd9af7c28