I don't see these ideas in RFCs:
* The match operator, C<m>, is always required (bare C<//> becomes a fatal
error).
* Replace C<??> with flag to C<m//>, and remove special meaning of C<m??>.
* Socket functions (such as C<accept>, C<bind>, etc) should be moved from
the core to modules/libraries.
* Math functions (such as C<abs>, C<atan2>, C<cos>, etc) should be moved
from the core to modules/libraries.
* Remove deprecated commands C<dbmopen> and C<dbmclose>.
* IPC functions (such as C<msgctl>, C<semctl>, C<shmctl>, etc) should be
moved from the core to modules/libraries.
* "User" functions (C<getpw*>, <endpw*>, C<setpw*>, C<getlogin>) should be
moved from the core to modules/libraries.
* Group functions (C<getgr*>, C<endgr*>, C<setgr*>) should be moved from
the core to modules/libraries.
* Network functions (C<getnet*>, C<gethost*>, C<getproto*>, etc) should be
moved from the core to modules/libraries.
* Removed deprecated command C<dump>.
* Process functions (C<getpgrp>, C<getppid>, C<getpriority>, C<setpgrp>,
C<setpriority>) should be moved from the core to modules/libraries.
* 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).
* Disallow use of C</> as delimiters for quote functions and require use
of matching pair characters.
* Remove special meaning from C</>. Integrate that functionality with
C<'> and C<">.
* Remove C<y///> as a synonym for C<tr///>
Some of these are mine, some of them are ideas I remember seeing someone
else mention, but I don't see RFCs for. Am I missing them, or do they need
to be written up?
-spp
