OO for the sake of OO? No, thanks!

There is no point in turning this into an object! Look again at the resulting API ... it's awkward. It might make sense to implement class Google::Charts that can load the data in several formats (encoded and not encoded or whatever), do something sensible with them, allow you to look at the details and then export the data in some formats ... one of them being this encoded string, but a class that has exactly one method and nothing you could really call internal state is bad design.

Keep it procedural and export the function on request!

Jenda
Enoch was right!
Enjoy the last years of Rome.

In reply to Re^2: Perl and Google Charts extended encoding by Jenda
in thread Perl and Google Charts extended encoding by PoliceCoP

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.