I see no problem with this, but: I would encourage that any Amber specific PMCS instead go into languages/amber/classes, in an effort to keep classes/ and dynclasses/ restricted to the basic parrot types. (see languages/tcl and config/gen/makefiles/tcl.in) for examples on how to set this up. Regards! Roger Browne writes:
The Amber compiler currently generates all its types as PIR objects, but
I'm considering implementing the basic types as PMCs instead.
If I do this, can I have the Amber PMCs included in the dynclasses
directory of the Parrot distribution? (Assigning copyright to the Perl Foundation would not be a problem).
Regards,
Roger Browne



Reply via email to