[qmtest] [PATCH] report syntax error in extension classes

Vladimir Prus ghost at cs.msu.su
Tue Oct 22 09:53:09 UTC 2002


Mark Mitchell wrote:

>> Hello,
>> now, if extension class contains a syntax error, then QMTest would just
>> say that this class is "not found", which makes it hard to understand
>> where in extension class the syntax error is. The attaches patch fixes
>> this. I'm not happy with error message formatting --- there are some
>> extra newlines, but I don't know how to fix it.
> 
> 
> Did you try the new "qmtest register" command?
> 
> This is the command used to register extension classes, and it should
> already give you a traceback if your extension class is invalid.

I was not aware of this command. It's very good that it appears. 
However, even after I register a class, I can still edit it, and get 
unclear error message. Moreover, the class may be edited by someone who 
has no idea about 'register'.

I've tried a different approach, adding the same reporting logic in 
QMTEst.__ExecuteRun as is in QMTest.__ExecuteRegister, so that errors in
extension are reported during runs. Do you think it's reasonable?

(The patch is attached)

- Volodya
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: extensions_syntax.diff
URL: <http://sourcerytools.com/pipermail/qmtest/attachments/20021022/c7fad632/attachment.ksh>


More information about the qmtest mailing list