Aaron Sherman skribis 2004-04-14 16:40 (-0400):
> >From a source tree I work with (which I cannot divulge code from, but I
> think statistics like this are fine):
> $ find . -name \*.pl | wc -l
> 330
> $ find . -name \*.pl -exec grep -hlE 'qx|`|`|readpipe' {} \; | wc -l
> 123
How many of those backticks are in documentation or string literals? In
my @INC I found a lot of attempts to get balanced single quotes in ASCII
as like `foo'.
And how often are simple hash subscripts used?
Also, how insecure and/or inefficient is this code? In #perlhelp, on
PerlMonks and in many other places, backticks are discouraged.
> operators, and I see qx{} as just as good if not better, but to remove
> it on the basis of the lack of use is faulty.
Removing and replacing the meanings of glyphs on the basis of use is
one of the most important changes in Perl 6.
After all, -> becomes . and -> gets a new meaning.
| becomes +| (or ~|, ?|) and | gets a new meaning.
Etcetera.
Lack of use as a reason for changing something is not faulty, it is
exactly what should be done.
BUT `` do not have to go because I have ` in mind for something else.
The two things can co-exist, as Matthijs pointed out with his Perl 5
patch. I think it has to go because `pwd`, `hostname`, `wget -O - $url`
should not be easier than the purer Perl equivalents and because ``'s
interpolation does more harm than good.
> I would have preferred that Perl 6 used the bash/zsh-style:
> $(...)
It's just one keyword and a set of quotes more: $( readpipe "pwd" )
Juerd
