Re: RFC 164 (v1) Replace =~, !~, m//, and s/// with match() and subst()

2000-08-28 Thread Chaim Frenkel
t defaults to perl5 compat). The reason for MM> having 'use' instead of 'require' is that the interpreter can turn on MM> compile-time warnings / optimizations as it goes from module to module. MM> Maybe this should be an RFC. MM> -Michael -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 110 (v3) counting matches

2000-08-29 Thread Chaim Frenkel
d to pattern matching. TC> Furthermore, it's inarguably more mnemonic for the sense of "match this TC> scalarishly". -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 165 (v1) Allow Varibles in tr///

2000-09-03 Thread Chaim Frenkel
unicode, and I don't know anything about it, but I do know that 256 chars are a bit limited to accomplish that task. And extentions to handle classes will probably be needed? Hmm, has anyone started a -unicode list? -- Chaim Frenkel

Re: \z vs \Z vs $

2000-09-20 Thread Chaim Frenkel
rong". Sorry, I'm missing it. $_ = "etc\n"; /etc$/; # true $_ = "etc"; /etc$/; # true In what way is this _wrong_? Is it under /m? But then wouldn't longest match cover the situation? And doesn't it o