And if you are taking the trouble to look at my code I would appreciate your comment on something else that is bothering me.
The FSA has two attributes, fsa_states and fsa_transitions which define the rules for the Finite State Automata and anyone wishing to use this Role has to provide the two build methods, _build_fsa_states and _build_fsa_transitions. This seems clumsy to me so I would welcome any suggestions on how to do this differently. Kind Regards Ian -----Original Message----- From: Docherty, Ian (IT/UK) Sent: 19 September 2011 14:55 To: moose@perl.org Subject: RE: MooseX::FSA::Simple I should have shown the code first, but was too embarrassed because it has no pod (working on it now) and limited tests, but you can see what there is at https://github.com/icydee/moosex-dfa-simple if you care. Thank you. Ian -----Original Message----- From: Stevan Little [mailto:stevan.lit...@iinteractive.com] Sent: 19 September 2011 14:21 To: Richard Simões Cc: Docherty, Ian (IT/UK); moose@perl.org Subject: Re: MooseX::FSA::Simple Richard, Actually it seems that most of the MooseX::Role modules (http://search.cpan.org/search?query=MooseX::Role&mode=all) are not that. Some of them do extend the Role API, but most seem to provide some level of basic features that can be mixed into an object. In some cases this is an inappropriate use of the MooseX::Role namespace and in others I think it straddles the line. For instance, MooseX::Role::TraitsConstructor is not extending the Role API, but I am not sure that would make sense to be named anything different. I think really it depends on what exactly Ian's module does here. Ian, care to share the code? - Stevan -- This e-mail (including any attachments) is confidential, may contain proprietary or privileged information and is intended for the named recipient(s) only. Unintended recipients are prohibited from taking action on the basis of information in this e-mail and must delete all copies. Nomura will not accept responsibility or liability for the accuracy or completeness of, or the presence of any virus or disabling code in, this e-mail. If verification is sought please request a hard copy. Any reference to the terms of executed transactions should be treated as preliminary only and subject to formal written confirmation by Nomura. Nomura reserves the right to monitor e-mail communications through its networks (in accordance with applicable laws). No confidentiality or privilege is waived or lost by Nomura by any mistransmission of this e-mail. Any reference to "Nomura" is a reference to any entity in the Nomura Holdings, Inc. group. Please read our Electronic Communications Legal Notice which forms part of this e-mail: http://www.Nomura.com/email_disclaimer.htm
