#8: Various issues with get_class interface
-----------------------+----------------------------------------------------
Reporter: pmichaud | Owner: whiteknight
Type: todo | Status: closed
Priority: major | Milestone: 0.9.1
Component: core | Version:
Severity: medium | Resolution: fixed
Keywords: get_class | Lang:
Patch: | Platform: all
-----------------------+----------------------------------------------------
Changes (by whiteknight):
* status: assigned => closed
* resolution: => fixed
Comment:
I'm decently certain that this issue is mostly fixed. The two examples
that pmichaud posted above now act the way I would expect them to act. The
first prints "1\n1", and the second throws an exception because the given
class can't be found because it doesn't exist.
The internals are still a little hacky because Roles aren't handled
properly. However, all the rest of the data items aren't stringified first
which is something pmichaud said was bad. So, Roles are the only PMCs that
are still handled that way, but we can redo their handling later when we
run into problems for it. Issue resolved.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/8#comment:8>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
