Simon Cozens makes a good point in response to my slightly overamped
oration on the qualities of dissent.
I am seeing most of the current discussion on this list as being
brainstorming on details, not painting the vast new blue skies,
and that is as it should be.
Acknowledging that making change
Simon Cozens writes:
>> However, we are not designing Perl 5.
This gets to a theme that is turning into more and more of an
irritant in following (and very occasionally participating) in the
ongoing discussion here.
There seems to be a sense among some participants that certain issues
are Off L
I just want to say it seems appropriate that this discussion of how
Perl can look like Morse Code is happening in the thread I first started,
since I was active in ham radio from 1970-95 (mostly CW, or "Morse Code"
to you non-hams).
And consider it a blessing that Perl can look like Morse Code, n
I have a different suggestion:
replace -> with ~
~ is already Perlish for "glues to something related".
That's a different construct than "concatenates."
Fred
A vote against the proposed switches, for an unbearably lazy (ok,
"selfish") reason. Having to use the shift key with any non-alphanumeric
keypress always feels like a lot of extra work. This is why I have long
avoided underscores in variable names. (This is the same reason
I avoid => which not
Bart Lateur's response summarizes well what I've heard so far
from responses both to the list and privately:
(1) Yes, ~ *is* somewhat used in its current role as the bitwise
negation (complement) operator.
(2) No, that doesn't appear to overlap my proposal for its use
as a successor to
It seems to me that ~ relates to forces (operators, functions and methods)
more than to atoms (scalars), so to speak. It's the curve of binding Perl
at work here.
So why not leave . alone and have ~ substitute for ->
$mydsn->Sql("$mysqlstmt " . $moresql) ;
$mydsn~Sql("$mysqlstmt " . $mores
