Richard Heck wrote:
> I guess we'd better hold 2.0.7 until this is fixed....

Stephan's workaround seems to be just fine for that purpose. At least it looks 
innocent enough.

Regards,
Jürgen

Reply via email to