On Jan 24, 2008 9:02 AM, Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
> On Thu, Jan 24, 2008 at 11:58:02AM -0500, Mark J. Reed wrote:
> > Sorry if I'm missing something here, since I haven't dived into the
> > innards of Parrot, but I thought control flow in Parrot was based on
> > continuations? Presumably 'control exceptions' are really just
> > lexicaly-scoped exceptions, and exceptions are in turn just
> > outgoing-only continuations. If you have first-class continuations,
> > goto should be pretty straightforward to implement...
>
> You're probably correct about this... as I mentioned, I just hadn't
> thought about it too heavily yet. At the moment, 'goto' is waaaaay
> down on the list of things I've been thinking about ('return', 'next',
> 'last', etc. are much higher).
>
and 'warn', which is not an outgoing-only continuation.
~jerry
