>Normally, no. But when you experience the number of issues you've had, it indicates there is something very wrong with the way it's done.

I agree, but it's difficult to have a support for a portion of code that does not exist. The situation was an isolated one and has been addressed. It took a few adjustments in 3 to 4 lines of code. I always try to fix things and make the product evolve but there was various criterias that have to be respected such as funding, priority of assignments, support of existing client applications that use the class and so on. For example, in this case, this was isolated in about 10 lines of code but a change in there requires about 8 to 10 days of testing.