On Thu, 09 Jul 2009 21:28:14 -0700, Chip Salzenberg wrote: > This is an amusing discussion. > > The only problem that I observe with scalar split writing to @_ > implicitly is that it's an easy thing to do by accident and is almost > never useful. Therefore, removing it seems a public service. > > I favor simply making it a compile-time error to use split in scalar > context. No problem with silently changing semantics and no more > surprising behavior. Everybody's happy. (right?) I don't get it. The docs say that scalar split returns the number of elements. That's useful and convenient, and more intuitive than some of the alternative gyrations that have been suggested. No one cares about it shoving the contents in @_ or wants that to continue, especially since it results in a warning. So why can't we make it return the number of elements without either populating @_ or generating a warning? -- Peter ScottThread Previous | Thread Next