Larry,
Good point. This one is not too serious — the workaround is to always pass
an opaque – type parameter as VAR. What bothers me is (1) this workaround
didn't USED to be necessary, and (2) the compiler error generated was obscure
enough that I spent a lot of time trying to figure out what was really wrong!
The error code said something to the effect that the implementation of the
procedure did not match its definition. From this I infer that TDI put
information (erroneously) into the .SYM file to expect a VAR parameter for
the opaque type.
Oh well…
GAry