Will Coleda apparently needs to actually read all of his mail in the morning
before replying to it.
^_^
Will Coleda writes:
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 dynclasse
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.
On Tue, 2005-09-27 at 15:11 +0200, Leopold Toetsch wrote:
> Have a look at languages/tcl/classes - it contains Tcl PMCs. We could do
> the same for languages/amber.
Thanks - now I just need to learn to program in C :-)
Roger
Roger Browne wrote:
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?
Have a look at languages/tcl/class
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
