view release on metacpan or  search on metacpan

README  view on Meta::CPAN

        and doesn't have the stigma associated with other "comefrom"s.
        Instead, it installs a post-processing handler for the subroutine,
        and a jump would be made just *after* the subroutine's execution.

    If two or more "comefrom" were applied to the same LABEL, EXPR or NAME,
    they will be executed simultaneously via "fork()". The forking are
    ordered by their occurrances, with the parent process receiving the last
    one.

BUGS
    This module does not really parse perl; it guesses label names quite
    accurately, but the regex matching the "comefrom" itself could catch
    many false-positives. Perhaps some day a brave soul somewhere will
    volunteer to patch this module to use PPI instead...

ACKNOWLEDGEMENTS
    To the INTERCAL language, for its endless inspiration.

    As its manual states: "The earliest known description of the COME FROM
    statement in the computing literature is in [R. L. Clark, "A linguistic
    contribution to GOTO-less programming," Commun. ACM 27 (1984), pp.

lib/Acme/ComeFrom.pm  view on Meta::CPAN

=back

If two or more C<comefrom> were applied to the same LABEL, EXPR or NAME,
they will be executed simultaneously via C<fork()>.  The forking are
ordered by their occurrances, with the parent process receiving
the last one.

=head1 BUGS

This module does not really parse perl; it guesses label names quite
accurately, but the regex matching the C<comefrom> itself could catch
many false-positives.  Perhaps some day a brave soul somewhere will
volunteer to patch this module to use L<PPI> instead...

=head1 ACKNOWLEDGEMENTS

To the B<INTERCAL> language, for its endless inspiration.

As its manual states:
"The earliest known description of the COME FROM statement in the computing