in reply to Re: •Re: Re: •Re: ftp, and store file in memory instead of persist to disk
in thread ftp, and store file in memory instead of persist to disk

Is IO::String a core module of 5.8, no, at least not with active state perl 5.8.0.
From 5.8's perlfunc: 
               File handles can be opened to "in memory" files
               held in Perl scalars via:

                   open($fh, `>', \$variable) || ..

[download]
Sorry. I misread somewhere that this had been implemented by putting IO::String in the core, but apparently it's a reimplementation as PerlIO::scalar.

why you suddenly turned this into personal attack
I didn't turn this into a personal attack. Apparently, you haven't read my standard disclaimer, as indicated in the footer of every recent message.

This isn't about you, as much as you might think it is. It's about ending behavior that is overall damaging to the community. When I have opinions about that, I speak them. It's certainly fair for you to comment about my opinions, but I notice you didn't actually challenge them. I would welcome that.

I would welcome your exchange about how reinventing a wheel and needlessly forking a good solution into two solutions, one of which has a limited use (yours) and the other is built from standard CPAN parts can be of benefit to the community. Instead, it seems like something that is harmful to me. And when something seems harmful, I am quick to raise the flag.

-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply.

  • Comment on •Re: Re: •Re: Re: •Re: ftp, and store file in memory instead of persist to disk
  • Download Code

Replies are listed 'Best First'.
RE: •Re: ftp, and store file in memory instead of persist to disk
by shotgunefx (Parson) on Feb 20, 2003 at 06:52 UTC
    I disagree that it's damaging to the community. While I agree with your advice to use IO::String, I think you are way off base telling him to keep his code to himself.

    What teaches you more? Typing a use statement or solving a problem? Should we not know how to make a fire because we have lighters? Furthermore, other people viewing such problems and solutions can learn from the experience as well about the way to do or not to do things. There are numerous problems that are neatly solved with CPAN but it doesn't teach most people anything at all. (Though it certainly makes them more productive) It's not like there are code reviews here of modules that might expose users to the how and why of the way things are, or should be done.

    If you don't feel like helping someone reinvent a wheel that's your prerogative but you have no right to tell someone to keep it to themselves because while you contribute more than most, it isn't your community but "our" community, and communities have a way of sorting these issues out all on their own.

    Now if the discussion here was about submitting this to CPAN, then that would be a different issue. Though given different but equally well implemented ends to the same means, my preference is for all of them to be available. There are reasons certain things get done over and over. Part of this of course is just to say you did, but often it's because the implementation disagrees with a potential users perspective of how the problem should be solved. I tend to think of writing code as writing any literature. People have their own perspective that shapes the work. If my perspective is different, should I do it your way because you did it first? Looking at problems from different perspectives is what got us out of the stone age.

    -Lee

    "To be civilized is to deny one's nature."
[reply]
      You apparently have not had to deal with the amount of cargo cult crap that I have. I suspect that when you have, you'll change your tune.

      Any posting becomes a potential meme. We can't afford to create more Matt Wrights out there. That's my point.

      -- Randal L. Schwartz, Perl hacker
      Be sure to read my standard disclaimer if this is a reply.

[reply]
        The 'use' mantra is perfectly reasonable at work, but the whole point IMHO of this site is to expand the user's Perl and general programming skills. The how and why. And using a module only covers the former. People cutting and pasting other peoples solutions are not my concern here. This isn't a CGI scripts repository, but if it were that attitude would be appropriate.

        -Lee

        "To be civilized is to deny one's nature."
[reply]

        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?

[reply]
Re: •Re: Re: •Re: Re: •Re: ftp, and store file in memory instead of persist to disk
by Anonymous Monk on Feb 20, 2003 at 13:25 UTC
    It's certainly fair for you to comment about my opinions, but I notice you didn't actually challenge them. I would welcome that.

    You're not going soft on us are you Randal? ;-)

[reply]
[reply]

        Heh, good to know. So do you program much in Python, I hear it's better than Perl ;-)

        </flamebait>

[reply]
[d/l]

In Section Cool Uses for Perl