A little of topic, but...

In C/C++ you do a file slurp with a open/mmap system call, and assign the resulting pointer to a collection object of your choice(char*,vector<whatever> or string). In fact, if your c++ programmers are any good, they should be able to handle most of the perl code you can throw at them, at least the idioms, without much problem. Doing it in C on the other hand....

Closeures are doable in C++, but its ugly and I believe it can't do everything(Could be wrong on that). Regexps can be a pain if they don't use a proper regexp library. Be careful with reblessing references into other classes, or dynamically changing @ISA(I cant think of any idioms that actually do that....).

just my 0.2 kroner

goldclaw

In reply to Re: Re: Idioms considered harmful by goldclaw
in thread Idioms considered harmful by rinceWind

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.