Stephen P. Potter writes:
> * The match operator, C<m>, is always required (bare C<//> becomes a fatal
> error).
I could live with that. Damian's done some work trying to tokenize
Perl and knows what the weird edge cases are. Damian, can you post
your short list?
> * Replace C<m//>, C<tr///>, and C<s///> with equivalent regularized
> functions that take mulitple arguments instead of using specialized
> syntax. It would be best if the names could be more "complete", like
> match(), translate(), and substitute() (although translate and substitute
> are rather long).
I think you'll lose that battle. Perl's tight RE integration is a
plus, not a minus. There are already long names for matching and
substitution if you use the Regexp module.
> * Disallow use of C</> as delimiters for quote functions and require use
> of matching pair characters.
Not sure what this would win. It's not really a parsing problem.
> * Remove special meaning from C</>. Integrate that functionality with
> C<'> and C<">.
Which special meaning? Division? :) This comes under the
m-always-mandatory category.
Nat
