Comments on: Use scalar references to pass large data without copying. http://www.effectiveperlprogramming.com/blog/298 Effective Perl Programming - write better, more idiomatic Perl Wed, 28 Dec 2011 08:06:47 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: brian d foy http://www.effectiveperlprogramming.com/blog/298/comment-page-1#comment-102 brian d foy Wed, 01 Dec 2010 14:33:08 +0000 http://www.effectiveperlprogramming.com/?p=298#comment-102 I think you forgot to read the first half of the article and my discussion of <code>@_</code>. It explains what you've misunderstood. I think you forgot to read the first half of the article and my discussion of @_. It explains what you’ve misunderstood.

]]> By: cmyker http://www.effectiveperlprogramming.com/blog/298/comment-page-1#comment-101 cmyker Wed, 01 Dec 2010 13:34:42 +0000 http://www.effectiveperlprogramming.com/?p=298#comment-101 brian, this behavior, in my opinion, affects Perl's performance and memory usage because Perl copies all non-referenced subroutines arguments to another address in memory. Of course programmer may avoid this if necessary by passing argument by reference as you mentioned above, but it is rarely used by Perl programmers (or your code will be full of "\" characters and besides Perl programmers are not C programmers which are get used to pointers because of C nature). brian, this behavior, in my opinion, affects Perl’s performance and memory usage because Perl copies all non-referenced subroutines arguments to another address in memory. Of course programmer may avoid this if necessary by passing argument by reference as you mentioned above, but it is rarely used by Perl programmers (or your code will be full of “\” characters and besides Perl programmers are not C programmers which are get used to pointers because of C nature).

]]> By: brian d foy http://www.effectiveperlprogramming.com/blog/298/comment-page-1#comment-100 brian d foy Wed, 01 Dec 2010 13:05:41 +0000 http://www.effectiveperlprogramming.com/?p=298#comment-100 I think you're confusing the copy-on-write semantics with maintaining a single reference to the same data. Perl let's you have it both ways so you can choose what you would like to do. Of all the disadvantages that Perl might have, I don't think this is a major one. :) I think you’re confusing the copy-on-write semantics with maintaining a single reference to the same data. Perl let’s you have it both ways so you can choose what you would like to do.

Of all the disadvantages that Perl might have, I don’t think this is a major one. :)

]]> By: cmyker http://www.effectiveperlprogramming.com/blog/298/comment-page-1#comment-99 cmyker Wed, 01 Dec 2010 11:22:50 +0000 http://www.effectiveperlprogramming.com/?p=298#comment-99 This is definitely one of the major Perl disadvantages :sad: . Python and PHP are using lazy coping mechanism (aka copy-on-write). Hope Perl 6 will use it too. This is definitely one of the major Perl disadvantages :sad: . Python and PHP are using lazy coping mechanism (aka copy-on-write). Hope Perl 6 will use it too.

]]>