You mean cargo-cult as in

"Lines 1 through 3 begin nearly every program I write, enabling warnings, turning on the common compiler restrictions (mandatory for programs longer than 10 lines), and disabling the buffering of standard output.".

Or meme's like

"Yes, purists may point out that dbmopen is officially ``deprecated'', but it's still the most convenient interface...".

"Then I would rather..."

And yours is the only voice or opinion that counts?

"...that you not post your buggy code here..."

You might at least do him and us the courtesy of pointing out the bugs... but then doing that for free won't help you with your laywers bills...

", especially when a much simpler solution is available."

Available where? It may be that with the use of the modules that you name, and if the OP or those that might come along and use his code are in control of the perl distributions they have to use, and have 5.8 available to them, then it would be possible to write a simpler solution. Assuming they have your encylopeadic knowledge of those modules and facilities you cite.

Otherwise, I don't see you pointing to a readily available solution, not does my quick search reveal one. The OP's code is written, is available, does work. Yes, I tried it. Did you?

Why does a 40-something with "...2 decades of experience...", with sufficient profile to allow him boast of a lifestyle--regular Caribean Cruises, flying all over the country and the world, despite his self-inflicted financial wounds--that many of the monks here envy, feel the need to continue to vilify the mistakes made by one 15? y/o, 5 years ago who tried to help his fellow netizen's by giving away some code he wrote?

In reply to Re: •Re: RE: •Re: ftp, and store file in memory instead of persist to disk by Anonymous Monk
in thread ftp, and store file in memory instead of persist to disk by pg

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.