Just so we don't rehash issues that are already covered in other RFC's,
since many are:
> =item perl6storm #0015
>
> merge tie and overloading. python's ease of doing this
> makes this embarrassing.
RFC 200: Objects: Revamp tie to support extensibility (Massive tie
changes)
> =item perl6storm #0021
>
> make the User::pwent style by-name hash object returns
> the default
RFC 259: Builtins : Make use of hashref context for garrulous builtins
RFC 73: All Perl core functions should return objects
> =item perl6storm #0033
>
> Should == on strings (wrong type) turn into eq?
RFFC 54: Operators: Polymorphic comparisons
> =item perl6storm #0034
>
> Find an easier way to write the prefix dereffers. infix
> easier for brain to read for left-to-write stack-based cognitive
> reasons.
>
> @{ (some_expression_here) }
RFC 134: Alternative array and hash slicing
> =item perl6storm #0035
>
> Make A->B place A in string context, like => does.
> That way no A()->B naughtiness.
RFC 244: Method calls should not suffer from the action on a distance
> =item perl6storm #0036
>
> Allow
>
> print $fh[$i] "whatever\n"
>
> to work.
RFC 174: Improved parsing and flexibility of indirect object syntax
> =item perl6storm #0041
>
> People don't grok <>. They think
>
> while (<>)
>
> will localize $_, or that <> by itself will assign to it!
RFC 129: Replace default filehandle/select with $DEFOUT, $DEFERR, $DEFIN
- covers the "while(<>)" part of the issue
RFC 215: More defaulting to $_
- covers the "$_ = <>" part of the issue
> =item perl6storm #0046
>
> make open work on URLs.
RFC 14: Modify open() to support FileObjects and Extensibility
RFC 100: Embed full URI support into Perl
> =item perl6storm #0053
>
> Make <DIRH> call readdir() just as <FILEH> calls readline().
RFC 14: Modify open() to support FileObjects and Extensibility
> =item perl6storm #0054
>
> Add dup() and dup2() style stuff to give legible ways of
> handling &FH and &=FH.
RFC 14: Modify open() to support FileObjects and Extensibility
> =item perl6storm #0065
>
> Make indirect objectable built-ins overloadable/overrideable/inheritable
> by object type.
Working on it already...have an upcoming RFC on embedded objects
> =item perl6storm #0067
>
> Where's ferror()? Can we raise exceptions on them?
>
> use io_errors; # wrong name
>
> or maybe
>
> STDOUT->raise_on_error
RFC 14: Modify open() to support FileObjects and Extensibility
- talks about filehandle methods, of which this could be one
> =item perl6storm #0071
>
> How do you prototype split? print?
RFC 174: Improved parsing and flexibility of indirect object syntax
- covers the print issue
> =item perl6storm #0104
>
> Look at the deep magic seen in some of the examples in Camel-3's
> OO and tie chapters and in perltootc. Consider what to canonize
> into a simpler-to-get-at mechanism, just as plum engendered much
> in perl5.
RFC 200: Objects: Revamp tie to support extensibility (Massive tie
changes)
And an upcoming RFC by myself on embedded objects
-Nate
