All the Perl that's Practical to Extract and Report
use Perl Log In
autrijus (1505)
Day 187 (r6222): Visiolizing the MetaModel.
::Class. It's available in two formats:
- Static PNG
- GIF animation of the bootstrapping process, made by Stevan
Much thanks to #perl6 and #parrot folks for encouragement and feedback. Please refer to this previous journal for the origin of those gnostic names. Stevan's new Mini MetaModel is a much more readable Perl 5 implementation -- bootstrapped and tested in less then 200 lines!
Other documents under the same directory are helpful, too, including Stevan's 10k ft view and kolibrie's 20k ft view.
On the PIL2JS front, iblech sped up compilation by 300%+, and the compiler now takes much more reasonable amount of memory. He also hacked in junctive autothreading inhibition for Bool parameters, returning out of multiple blocks, and various other nifty things.
fglock polished the Array container and List value implementation for the Perl5 runtime, and plans to expand his work on other container and value types.
That's it for today. See you tomorrow!
Or is it a BUG?"
"Let's call it an accidental feature. :-)"
--Larry Wall in <6909@jpl-devvax.JPL.NASA.GOV>
no gnosis; (Score:2)
Re:no gnosis; (Score:2)
On the other hand, the metaclass object ::Point itself -- on the left-hand side -- is an instance of ::Class, as shown by the dotted line.
Class versus metaclass (Score:2)
Re:Class versus metaclass (Score:2)
Conceptually, if we are implementing perl6 on perl6, then sure ::Class is just the metaclass itself.
But if you are, say, implementing perl6 on perl5 (which is what we're doing now), then you need a perl5-side entity to represent a perl6 class. That's what the MetaClass is.
Otherwise, you can't communicate with other perl5 objects -- "native" ones like DBI.
But it is that exact entity