<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.5" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Moose with Rose::DB::Object. Roose? Morose?</title>
	<link>http://blogs.aarohan.biz/2009/05/07/moose-with-rosedbobject-roose-morose/</link>
	<description>Writings on Linux, Perl and related topics from Aarohan Tech</description>
	<pubDate>Fri, 30 Jul 2010 22:03:28 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: John</title>
		<link>http://blogs.aarohan.biz/2009/05/07/moose-with-rosedbobject-roose-morose/#comment-37709</link>
		<pubDate>Thu, 07 May 2009 12:20:34 +0000</pubDate>
		<guid>http://blogs.aarohan.biz/2009/05/07/moose-with-rosedbobject-roose-morose/#comment-37709</guid>
					<description>One issue you may encounter is that both Moose and Rose::DB::Object define and rely on a method named meta().  (For the record, Rose::DB::Object had it first.)  This means that you can't make a Rose::DB::Object-derived class that also inherits from Moose, and you can't make a Moose class that inherits from a Rose::DB::Object-derived class.

What people usually do instead is use composition rather than inheritance.  That is, make a Moose-derived class that "has a" Rose::DB::Object-derived object within it, rather than one that "is a" (i.e., inherits from) Rose::DB::Object.  The reverse will also work: a Rose::DB::Object-derived object that "has a" Moose-derived object.

Good luck!  And don't forget about the Rose::DB::Object mailing list if you run into any problems: http://groups.google.com/group/rose-db-object</description>
		<content:encoded><![CDATA[<p>One issue you may encounter is that both Moose and Rose::DB::Object define and rely on a method named meta().  (For the record, Rose::DB::Object had it first.)  This means that you can&#8217;t make a Rose::DB::Object-derived class that also inherits from Moose, and you can&#8217;t make a Moose class that inherits from a Rose::DB::Object-derived class.</p>
<p>What people usually do instead is use composition rather than inheritance.  That is, make a Moose-derived class that &#8220;has a&#8221; Rose::DB::Object-derived object within it, rather than one that &#8220;is a&#8221; (i.e., inherits from) Rose::DB::Object.  The reverse will also work: a Rose::DB::Object-derived object that &#8220;has a&#8221; Moose-derived object.</p>
<p>Good luck!  And don&#8217;t forget about the Rose::DB::Object mailing list if you run into any problems: <a href="http://groups.google.com/group/rose-db-object" rel="nofollow">http://groups.google.com/group/rose-db-object</a>
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
