summaryrefslogtreecommitdiff
path: root/_posts/2009-06-30-private-and-protected-methods-with-moose.textile
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--_posts/2009-06-30-private-and-protected-methods-with-moose.md (renamed from _posts/2009-06-30-private-and-protected-methods-with-moose.textile)4
1 files changed, 2 insertions, 2 deletions
diff --git a/_posts/2009-06-30-private-and-protected-methods-with-moose.textile b/_posts/2009-06-30-private-and-protected-methods-with-moose.md
index 3734fe3..fe098f7 100644
--- a/_posts/2009-06-30-private-and-protected-methods-with-moose.textile
+++ b/_posts/2009-06-30-private-and-protected-methods-with-moose.md
@@ -1,6 +1,6 @@
---
layout: post
-category: perl
+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.
@@ -44,5 +44,5 @@ done was this:
with_caller => [qw( private protected )],);
{% endhighlight %}
-and write the 'private' and 'protected' sub. I'm sure there is some stuff I can do to improve this, but for a first test, I'm happy with the result and still amazed how easy it was to add this two keywords.
+and write the `private` and `protected` sub. I'm sure there is some stuff I can do to improve this, but for a first test, I'm happy with the result and still amazed how easy it was to add this two keywords.