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

So 'copying without regard to whether writing will ever occur or not'-,

???? I said not copying because there is no write is special case of COW.

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

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

    My mistake.

    So it's 'not copying for any reason' that is a special case of COW.

    Now it all makes sense.

[reply]

      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.

[reply]

        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]

In Section Seekers of Perl Wisdom