Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • ... there's often a balance between what the language or current design or available libraries let you do and how best to model the particular view of the universe which best matches the problem you're attempting to solve. All metaphors are lies.

    With that said, the internal implementation of an object system (especially a metaoperator protocol) won't match the problem domain of user code, because it has to model how objects and methods and roles and classes and prototypes and introspection and reflection w

    • All metaphors are lies.

      I prefer to think of them as useful fictions that illuminate a particular aspect of the truth. It is why good fiction is more true than bad non-fiction.

      With that said, the internal implementation of an object system (especially a metaoperator protocol) won't match the problem domain of user code

      Nor should they. MOPs especially are design to model the problem domain of an Object System. I've had a lot of serendipity about this recently, I hope I can get it all into my talk at YAPC which is about exactly this.