in reply to [Perl 6] Method call versus function call on a data set

I have to agree with the sentiment (discomfort?) described. I am uncomfortable with the idea of my 'container' doing anything other than 'containing'. I like the idea of my array simply being an array in which I can store things.

For me, this is analogous to putting a can of peas into a (container) pan, and having the pan heat them up for me. I don't want a pan that heats, I have a stove to do that for me. I want the pan to hold the peas until I decide to put them elsewhere. Of course, we have now had electric pans for some time, and I have learned to use them (rarely) and find them handy (also rarely). I prefer to leave my stove plugged in, and not have to plug(unplug) my pan. Sometimes simpler is better. I rarely need to move the stove, but often need to move the pan, and if the darn thing is plugged in, I may end up burning myself!

Perhaps this is silly..., so be it. I don't want my array to be smart. (nothing against those who do want that though)

I like that Perl gives me the ability to state what I have, the form that it is in, and allows me to do with it as I wish, rightly or wrongly. It has nouns and verbs and I can write my sentences and paragraphs as I see fit. I do not like the idea of someone handing me a paragraph (object) and telling me I now have to mold that paragraph to fit my context or intent. I find that limiting and typical of the OO code that I have dealt with.

I am however eternally grateful to those that have written those numerous modules that I make use of, most all of which are OO.

Thanks for the thoughtful post and responses. Enlightening as always...

  • ...the majority is always wrong, and always the last to know about it...
  • The Spice must flow...
  • ..by my will, and by will alone.. I set my mind in motion
  • Comment on Re: [Perl 6] Method call versus function call on a data set