Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl: the Markov chain saw

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

Ask yourself: Do you have an itch to scratch? Do you have some particular problem you need to solve?

If you don't, chances are that whatever particular cool module you start making or maintaining, you'll quickly lose all interest in it and it becomes a burden -- unless you really have that much extra time in your hands. It's symptomatic that you can't put a name on any topic that would interest you. Usually (of course not always) this means that you are raring to do something, but once you have that something to work on, it's not what you want. (Case in point: PDF::Writer.)

On the other hand, if you accept requests, I could use Perl bindings to libogg and libvorbis -- mind you, something more Perlish than converted C interface. The goal: being able to effetively manipulate audio data in Perl, the first step being able to decode audio data and then, after processing, encode it again. This is relatively simple and you would gain some XS and C experience in the meantime.

(I had some ready code for this, but my harddrive had a mechanical failure, and since then I've noticed that there's no burning need to have it after all. But it would be nice to have. If the module even supported loading data directly into piddles, the more the better!)

print "Just Another Perl Adept\n";

In reply to Re: Finding a module to work on by vrk
in thread Finding a module to work on by johnlawrence

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, 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, 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.
  • Log In?

    What's my password?
    Create A New User
    [Corion]: But my conundrum currently is how to do lightweight SQL for maintaining my user database, instead of home-cooking too much of an ORM ;)
    [Corion]: But maybe Just Enough of an ORM might be the ticket, that is, just locked hashes read from the DB :)

    How do I use this? | Other CB clients
    Other Users?
    Others browsing the Monastery: (10)
    As of 2018-03-21 12:09 GMT
    Find Nodes?
      Voting Booth?
      When I think of a mole I think of:

      Results (267 votes). Check out past polls.