I notice the following paragraph, vintage late May, in
pdd23_exceptions.pod:

        A C<.begin_eh> directive marks the beginning of a span of
        opcodes which the programmer expects to throw an exception.  If
        an exception occurs in the execution of the given opcode span,
        Parrot will transfer control to I<LABEL>.

I assume this means that you intend to replace the current methodology
of searching for an Exception_Handler object on the control stack when
an error is thrown with a search through sub metadata.  How do you
envision this interacting with C<pushaction>, e.g.?  Currently, it is
straightforward for find_exception_handler to DTRT WRT other control
stack entries.  Would the metadata also contain information about
C<pushaction> and such?

   TIA,

                                        -- Bob Rogers
                                           http://rgrjr.dyndns.org/

P.S.  FWIW, I am asking now because I have begun to work again on
dynamic binding -- which of course makes this problem worse.

Reply via email to