dynoplibs in core or no?
wknight8111 at gmail.com
Tue Jun 1 17:55:22 UTC 2010
On Tue, Jun 1, 2010 at 1:41 PM, Michael Hind <mike.hind at gmail.com> wrote:
> We really need to consider what constitutes the "core" of parrot.
> This is what is tested by make corevm/make coretest
> Extensions are generally not considered part of the "core".
> As regards, dynops and dynpmcs, I would probably not consider them part of
> "core", but could go either way.
> The changes, both with the ops massacre and opsc, have moved a lot of things
> around and I think we seriously need to re-evaluate where we stand here.
Good points. I really feel that "core", at least as it pertains to the
"corevm" and "coretest" make targets should include just libparrot and
the Parrot executable. We need these targets to be as slim as possible
so that when we have done "make corevm" and "make coretest" we have a
solid base upon which we can start testing ever more abstract layers
of addon functionality.
More information about the parrot-dev