in reply to Re^8: returning large arrays from functions
in thread returning large arrays from functions

The copying would have to occur on write, except no writes occur when the buffer is still shared.

You've been doing nothing but misrepresenting what I've said. Ask questions if there's something you don't understand, but please stop putting words in my mouth.

  • Comment on Re^9: returning large arrays from functions

Replies are listed 'Best First'.
Re^10: returning large arrays from functions
by Anonymous Monk on Nov 19, 2010 at 16:31 UTC

    All the words come directly from your posts. No one but you put them there.

    The OPs question related to returning large volumes of data from subroutines. That inherently means that by the time the caller is running and has access to the returned data, the subroutines has ended. There can be no possibility of "shared access".

    In other words, your even mentioning the term COW in response to the OPs question is entirely vacuous. Citing it as a reason why Perl copies rather than aliases the returned data, completely erroneous. Terming "not copying" as a "special case of COW", fatuous.

    Continuing to defend those, is priceless.

[reply]
      Sorry, I won't continuestart to defend these falsely attributed statements. I didn't even speculate as to why Perl behaves as it does.
[reply]

        Denial. I guess it's progress.

        Not good progress since it's of the written record, but progress none the less.

[reply]

In Section Seekers of Perl Wisdom