> : In a void context, C<dump> dumps the program's current opcode
> : representation to its filehandle argument (or STDOUT, by
> : default).
>
> It's not clear to me that reusing a lame keyword for this is the
> highest design goal. Let's come up with a real interface, and then if
> we want to reuse the (the presumably missing) dump keyword for some
> method name or other, that's fine. But we're currently designing it
> from the wrong end.
You're not a Sapir-Whorfist then? ;-)
Actually, I wasn't proposing we design it at all.
Sarathy has already done rather a good job of that, I think.
Tom's opcode dumping functionality could, in principle, be added to
Data::Dumper as it stands.
My proposal was merely that C<&Data::Dumper::Dumper> body-snatch C<dump>.
Damian
