M
Mr P
shift split /\s+/, @$tx;
Type of arg 1 to shift must be array (not split) at
/production/fe/users/feot/acs/ACS_Spex.pm line 5, near "$tx )"
shift ( split /\s+/, @$tx );
(same error)
It doesn't make sense that I can do:
@array = arrayOp args
but I can't do
@array = arrayOp1 (arrayOp2 args)
**********************************************
Larry you almost always make things work as expected, but for
perlfunction "chains" like
op1 op2 op3 ... opn arg
everything is almost always busted. This is "the stuff" of clean,
concise syntax (chains) and they don't often work in Perl.
scalarOp (stuff)
should always try its best to turn "stuff" into a scalar
(precedence-rules followed of course)
Likewise,
arrayOp (stuff)
should always try its best to turn "stuff" into an array, coercing
lists if necessary
and of course likewise for hashes
This is particularly true when using parens around stuff- can't make it
much clearer than that to the parser!
Larry I've heard you say personally that your intended design on Perl
was that "things would always always work as you'd expect". That's true
for almost every simple case like
operator args
and not true for almost every compound case.
Get your knives out Uri et al, but this is annoying, depsite your
defense that Perl design is "always right", and comp scientsts opposing
views are "always wrong". (I've read myriad responses to that effect).
I'll do it in individual lines, whatever..
Rant --
Type of arg 1 to shift must be array (not split) at
/production/fe/users/feot/acs/ACS_Spex.pm line 5, near "$tx )"
shift ( split /\s+/, @$tx );
(same error)
It doesn't make sense that I can do:
@array = arrayOp args
but I can't do
@array = arrayOp1 (arrayOp2 args)
**********************************************
Larry you almost always make things work as expected, but for
perlfunction "chains" like
op1 op2 op3 ... opn arg
everything is almost always busted. This is "the stuff" of clean,
concise syntax (chains) and they don't often work in Perl.
scalarOp (stuff)
should always try its best to turn "stuff" into a scalar
(precedence-rules followed of course)
Likewise,
arrayOp (stuff)
should always try its best to turn "stuff" into an array, coercing
lists if necessary
and of course likewise for hashes
This is particularly true when using parens around stuff- can't make it
much clearer than that to the parser!
Larry I've heard you say personally that your intended design on Perl
was that "things would always always work as you'd expect". That's true
for almost every simple case like
operator args
and not true for almost every compound case.
Get your knives out Uri et al, but this is annoying, depsite your
defense that Perl design is "always right", and comp scientsts opposing
views are "always wrong". (I've read myriad responses to that effect).
I'll do it in individual lines, whatever..
Rant --