Michael Reitzenstein #1 OK thanks for the bug report. Any chance of any code that reproduces this error? It should be the single type declaration that does this, and with any chance it is just a simple error on my part that will be easily fixed.