Beefy Boxes and Bandwidth Generously Provided by pair Networks
We don't bite newbies here... much
 
PerlMonks  

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
I think there are lots of cases out there, and they are backed by Perl modules wrapped around C code.

For example, I'd never use XML::XPath in any project that used a largish XML file and needed to get done somewhere near quickly... but XML::LibXML works great, and still allows me to do my work in Perl.

Usually where the projects are going to fail is where speed becomes an issue, or where Perl isn't available, or memory issues. For the speed most people turn to wrapping C, the other two are a little tougher :)

                - Ant
                - Some of my best work - (1 2 3)


In reply to Re: Don't Write That In Perl! by suaveant
in thread Don't Write That In Perl! by Ovid

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



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.