[Bioperl-l] Interest in Bio::Community modules
florent.angly at gmail.com
Tue Nov 29 21:50:04 EST 2011
Fantastic! Thank you very much Chris,
On 30/11/11 12:34, Fields, Christopher J wrote:
> On Nov 29, 2011, at 7:18 PM, Florent Angly wrote:
>> Yes, it is exciting to learn something new.
>> I have developed a bit of code in the last few days in my local git repository. Do you think you could create a repository for Bio-Community on the Bioperl Github space or is it too soon?
> It's up to you. I set up the barebones repo and added you on to push/pull/admin, you should be able to push to it whenever you are ready:
>> On 30/11/11 05:11, Fields, Christopher J wrote:
>>> On Nov 28, 2011, at 6:59 PM, Florent Angly wrote:
>>>> Hi Chris,
>>>> On 29/11/11 05:47, Fields, Christopher J wrote:
>>>>> Re: using Moose and BioPerl, from experience it's a little tricky integrating the two as BioPerl uses perl's simple OO system while Moose allows much more (though it has it's own issues, memory and speed being the top two). Specifying inheritance from a BioPerl module is a bit trickier, you'll have to wrap the module via MooseX::NonMoose. Beyond that, I think if you stick with using is-a/has-a based relations for the time being when defining interactions with other BioPerl modules you'll be fine.
>>>> Beyond Bio::RootI, I cannot imagine that any of the Bio::Community::* modules would need to inherit from any other BioPerl modules. Considering this and the performance aspects of Moose, do you think that using Moose is a wise design decision?
>>> Moose can actually help in some circumstances; flattening the inheritance hierarchy by using roles seems to help. And it never hurts to learn something new like Moose and other modern perl niceties.
>>> Bioperl-l mailing list
>>> Bioperl-l at lists.open-bio.org
>> Bioperl-l mailing list
>> Bioperl-l at lists.open-bio.org
More information about the Bioperl-l