On Wed, Aug 16, 2000 at 04:49:15PM -0500, David L. Nicol wrote:
>
>
> or AUTOLOAD can be defined in terms of C
> and overloaded that way, rather than being its own
> kind of magic.
>
> catch "AUTOLOAD-$classname-$polymorphicsignature" {...
But why should I have to know that a sub I want
On Wed, Aug 16, 2000 at 12:15:30PM -0500, David L. Nicol wrote:
>
>If "catch" can be defined DURING PARSING
>
>and SYNTAX ERRORS are catchable
>
>error handling can be used to define otherwise
>undefined syntax, becoming a macro language.
Please take this to the -errors sublist. Thanks...
K.
-
or AUTOLOAD can be defined in terms of C
and overloaded that way, rather than being its own
kind of magic.
catch "AUTOLOAD-$classname-$polymorphicsignature" {...
Jonathan Scott Duff wrote:
>
> On Wed, Aug 16, 2000 at 12:15:30PM -0500, David L. Nicol wrote:
> > If "catch" can be def
On Wed, Aug 16, 2000 at 12:15:30PM -0500, David L. Nicol wrote:
> If "catch" can be defined DURING PARSING
>
> and SYNTAX ERRORS are catchable
>
>
> error handling can be used to define otherwise
> undefined syntax, becoming a macro language.
And AUTOLOAD can go away too! :-)
-Scott
--
Jona
If "catch" can be defined DURING PARSING
and SYNTAX ERRORS are catchable
error handling can be used to define otherwise
undefined syntax, becoming a macro language.
This would be similar to the RFC18 immediate subroutines,
as it would be another way to change the language of the
remainder o
