If you want to edit and not have those changes reflected, yes. However, when using the \@ prototype, my experience is that you usually want to have your changes reflected in the array when you're done. In fact, most examples in the docs regarding prototypes and arrays involve things like my_push() and my_pop(), which do change their parameters. YMMV
------
We are the carpenters and bricklayers of the Information Age.
Please remember that I'm crufty and crochety. All opinions are purely mine and all code is untested, unless otherwise specified.
| [reply] |
This is an excellent point and well put. However, 2 arrays *are* being passed in the example, which is the other important usage of array-prototypes that comes to mind. But, anyway, I dislike prototypes and would just like to see a ref passed in the first place, but that's just me.
,welchavw
| [reply] |