Historically Tcl has always stored all intermediate results as strings. (With 8.0 they're rethinking that. Of course, Perl rethought that from the start.)
Tcl tends to get ported to weird places like routers.
It's certainly easy to calculate the average attendance for Perl conferences.
I don't think it's worth washing hogs over.
If you remove stricture from a large Perl program currently, you're just installing delayed bugs, whereas with this feature, you're installing an instant bug that's easily fixed. Whoopee.
Anyway, my money is still on use strict vars . . .
I surely do hope that's a syntax error.
switch (ref $@) { OverflowError => warn 'Dam needs to be drained'; DomainError => warn 'King needs to be trained'; NuclearWarError => die; }
This has been planned for some time. I guess we'll just have to find someone with an exceptionally round tuit.
I wasn't recommending that we make the links for them, only provide them with the tools to do so if they want to take the gamble (or the gambol).
And we can always supply them with a program that makes identical files into links to a single file.
Magically turning people's old scalar contexts into list contexts is a recipe for several kinds of disaster.
P.S. I suppose I really should be nicer to people today, considering I'll be singing in Billy Graham's choir tonight...
Oh, wait, that was Randal...nevermind...
But the possibility of abuse may be a good reason for leaving capabilities out of other computer languages, it's not a good reason for leaving capabilities out of Perl.