> -----Original Message----- > Date: Mon 08/11/03 3:30 AM > From: Michal Wallace <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > CC: > Subject: help raise hell > > > > Here is how I usually trigger a generic exception > in python: > > >>> raise hell > Traceback (most recent call last): > File "<stdin>", line 1, in ? > NameError: name 'hell' is not defined > > Unfortunately, I can't seem to trap that in parrot, > because a find_lex failure isn't an exception. > Or am I missing something? > > > CAN trap this though: > > >>> raise 'hell' > > So it's not a showstopper, but still... > > Is this easily fixable? I miss my idiom... :)
How are you currently throwing/catching exceptions? I think it might be much more difficult to create a model that "traps" exceptions, rather than setting up code that just "figures out" how to handle an exception when it occurs. Both JVM->PIR and P6C use continuations to handle exceptions, albeit in different ways. Anyways, since I can't read python, could you explain what you are using now? (-: - Joe -- This message was sent using 3wmail. Your fast free POP3 mail client at www.3wmail.com
