Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Newer
Older
100644 40 lines (31 sloc) 1.533 kB
aa98294 Update README.md
Stevan Little authored
1 **NOTE: This project has been restarted under a different name, see https://github.com/stevan/p5-mop-redux for more info**
98f04ef updating the README
Stevan Little authored
2
aa98294 Update README.md
Stevan Little authored
3 # A MOP for Perl 5
024d2ae adding a README on the prototype
Stevan Little authored
4
adc1263 revise some READMEs and add a TODO
Stevan Little authored
5 This repository contains an ever evolving proposal and a
6 functioning prototype for a Meta Object Protocol, or MOP,
7 to be perhaps included in a future version of Perl 5.
98f04ef updating the README
Stevan Little authored
8
9 The core goal is to provide a simple, lightweight and
10 highly Perl-ish MOP that will provide the same degree of
11 flexibility and TIMTOWTDI of the original Perl 5 object
12 model, but with more a formalized class model.
13
14 This proposal will be developed in the open and comments
15 are welcome.
16
554e2a2 moving things around
Stevan Little authored
17 -----------------------------
2a16224 tweaking the readme a bit
Stevan Little authored
18 Prototype notes ...
19 -----------------------------
554e2a2 moving things around
Stevan Little authored
20
21 This is a prototype of the proposed MOP for Perl 5. The
22 main purpose of this prototypes is to work out a few
23 of key things; the syntax/semantics of the object
24 system, the underlying MOP API and the extensibility
25 of the MOP itself.
26
27 Ideally this will also provide the starts of a test
28 suite that can be ported to the final implementation.
29
30 This prototype, for the most part, accurately
31 reflects the proposed syntax/semanitics of the object
32 system, however the implementation is another story.
33 Basically, any implementation found in these folders
34 should *NEVER* be considered a proposal for a *specific*
35 implementation technique. In fact, much of what you might
36 find in here will likely use scary and tricky techniques
37 to accomplish desired behaviors, and it would be
38 expected that a real implementation would *NOT* use
39 such scary and tricky techniques.
Something went wrong with that request. Please try again.