|laziness, impatience, and hubris|
objects as closuresby Excalibor (Monk)
|on Jul 07, 2003 at 15:07 UTC||Need Help??|
And you should know, Abigail!!!
Actually, as Abigail just did (go quickly and grab Closures-1.2 in http://cpan.org/modules/by-authors/id/ABIGAIL/), you can construct a whole object system on top the closures (it's been done some dozen times in different ways in Scheme, where basically everything is a closure).
A simpler example, consider this code:
We create a closure which exposes the interface of the class and holds both the methods (in %self) and data (in %mem, from memory). Please, note that it's impossible to read or write to the values held in %mem or %self (ie, modify the state of the object or modify its interface) directly, only through the interface exposed, which is very hygienic in itself. Using this is easy (if somewhat not very idiomatic):
Output is as expected (text between 's is mine):
I am sure it's not too hard being able to force the dereference of the methods when you are on getter mode so instead of writing $john->('age')->() you can just say $john->('age') (as Abigail has in Closures-1.2). Probably an additional line checking the number of arguments passed to the method.
Except being the state held in the closures, this is all pure functional code; functional programming rules, yeah :)