Re^6: returning large arrays from functions

So 'copying without regard to whether writing will ever occur or not'--or as the rest of us like to call it, just "copying"--is to you a special case of copy on write.

Not just techno-babble used to dress up an otherwise meaningless post for no more purpose than XP-whoring.

Comment on Re^6: returning large arrays from functions

Replies are listed 'Best First'.
Re^7: returning large arrays from functions by ikegami (Patriarch) on Nov 19, 2010 at 14:20 UTC
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.	[reply]
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]
Re^9: returning large arrays from functions by ikegami (Patriarch) on Nov 19, 2010 at 15:28 UTC
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]
Re^10: returning large arrays from functions by Anonymous Monk on Nov 19, 2010 at 16:31 UTC
Re^11: returning large arrays from functions by ikegami (Patriarch) on Nov 19, 2010 at 21:04 UTC
Some notes below your chosen depth have not been shown here
Re^7: returning large arrays from functions by ikegami (Patriarch) on Nov 19, 2010 at 14:21 UTC
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.	[reply]