Re: Reopening builtin classes, redefining builtin functions?

The answer to your questions are:

All classes in Perl inherit from UNIVERSAL. So, if you want everyone to have a to_yaml method, do this:

{
    no strict 'refs';
    *{ "UNIVERSAL::to_yaml" } = sub {
        # Put some code here.
    };
}
[download]

To redefine a core function, do this:
```
{
    no strict 'refs';
    *{ "CORE::<funcname>" } = sub { ... };
}
[download]
```
Some functions require you to redefine in CORE::GLOBAL:: instead. There's no real rhyme or reason (from the outside looking in) - you can find more by looking at the appropriate documentation.
Perl6 will allow for redefinition of EVERYTHING under the sun, including syntax, yet have those redefinitions be scoped however you want. In other words, the default Perl6 language is just that - the default. TimToady and the rest of the design team has the idea that Perl6 will actually be a group of interrelated languages that can all talk to one another vs. just a single language. And, people will provide modules to extend the language vs. having to edit the source.

My criteria for good software:

Does it work?
Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

Comment on Re: Reopening builtin classes, redefining builtin functions? Select or Download Code