summaryrefslogtreecommitdiff
path: root/posts/2009-06-30-private-and-protected-methods-with-moose.md
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--posts/2009-06-30-private-and-protected-methods-with-moose.md (renamed from content/post/2009-06-30-private-and-protected-methods-with-moose.md)6
1 files changed, 0 insertions, 6 deletions
diff --git a/content/post/2009-06-30-private-and-protected-methods-with-moose.md b/posts/2009-06-30-private-and-protected-methods-with-moose.md
index a182a31..9d68717 100644
--- a/content/post/2009-06-30-private-and-protected-methods-with-moose.md
+++ b/posts/2009-06-30-private-and-protected-methods-with-moose.md
@@ -1,9 +1,3 @@
----
-date: 2009-06-30T00:00:00Z
-summary: In which I show how to write dummy private methods for Moose
-title: Private and protected methods with Moose
----
-
Yesterday, one of our interns asked me a question about private method in <a href="http://www.iinteractive.com/moose/">Moose</a>. I told him that for Moose as for Perl, there is no such things as private method. By convention, methods prefixed with '_' are considered private.
But I was curious to see if it would be something complicated to implement in Moose. First, I've started to look at how the 'augment' keyword is done. I've then hacked Moose directly to add the private keyword. After asking advice to <a href="http://blog.woobling.org/">nothingmuch</a>, he recommended me that I implement this in a MooseX::* module instead. The result is <a href="http://git.lumberjaph.net/p5-moosex-methodprivate.git/">here</a>.