Recoding to eliminate the need for PLSQL_NAME_RESOLUTION in 10g

Question

Up until now (in forms 6i) we've been using this workaround, as we have quite a lot of instances in forms libraries where a procedure in the library calls another procedure back in the form. We're now going to forms 10g and realise we need to recode, as this isn't recommended and the workaround isn't supported.
I've already replaced quite a few of the procedure calls in the libraries with execute_trigger commands, but am not sure what to do about those with parameters. For example, in 1 of our libraries we have:
procedure report_params(param1, param2) is
begin
null;
end;
further up in the library is a call to this proc. But this one's only there for compilation - at the moment, the procs in the forms (with the same name) override this one. They all have this library attached. For ones like this with no params, I've been using execute_trigger. But what's the neatest way to deal with the procedures with params?

Answer 1

Package variables work great. Create a package spec in your PLL library with the variables you need to pass. Then, you can address these variables from both the PLL procedures as well as from anywhere in the form.
However, be aware that each time you add another variable to the package spec, any form that uses any variable in the package spec must be recompiled.
If you use form parameters from the PLL procedure, you will need to use the Copy built-in to set their values. Due to the above problem, if you expect to be changing the list of package variables often, then maybe the form parameters is a better solution.