importPackage() bug in trunk

[Tim Larson <ti...@keow.org>]

There appear to be 2 bugs with importPackage() in flowcript in trunk.

If importPackage() is not placed before all other code lines, then it
acts imperative, importing the requested package again, even if it
has already been imported via a previous run of the script.
This causes "Ambiguous import" errors when you try to use the
imported classes on the second and following runs of a script.

Also, if a script calls importPackage() (even as the first code line
as required by the above bug) but then does not use any of the
imported classes on that run, then following runs which do attempt
to use the imported classes will get the "Ambiguous import" error.

Anybody familiar with the code to help track this down?

--Tim Larson