API wrapper best practices?

Iain C Docherty londonperlmongers at iandocherty.com
Sat Mar 23 17:03:36 GMT 2013

If you want to be really lazy, do what I did in a very similar circumstance.

I used Moose to create two classes, one which was a general purpose method
to access the api, and in which was a factory object that created a 'Row'
class. In that class I used the Moose Meta to create accessors on the fly
for each data attribute. Better in my opinion than returning a nasty hash.

- icydee

On 23 March 2013 16:36, Pierre M <piemas25 at gmail.com> wrote:

> Probably, additional methods should not be part of the wrapper layer,
> but should constitute a just-the-next-layer.

More information about the london.pm mailing list