Tk: Calling Module More than Once Creates Problems

Uggles has asked for the wisdom of the Perl Monks concerning the following question:

Currently, I have a perl program with a gui in Tk that is essentially a search application. In order to run the search the program parses a certain file type into xml which is done by calling a module that was written exactly for this purpose. The first time that I hit the search button of my gui it works exactly like it is supposed to, but after that the module that creates the xml returns an error saying a certain array hasn't been initialized. Is this a known issue with Tk and GUIs? I don't understand why there would be an issue if I am just calling a module for a second time which is unrelated to the first time.

Comment on Tk: Calling Module More than Once Creates Problems

Replies are listed 'Best First'.
Re: Tk: Calling Module More than Once Creates Problems by Anonymous Monk on Jul 25, 2013 at 03:17 UTC
I don't understand why there would be an issue if I am just calling a module for a second time which is unrelated to the first time. Because not everyone understands how scoping works Read Tutorials: Simple Module Tutorial, Variable Scoping in Perl: the basics, Coping with Scoping , Mini-Tutorial: Perl's Memory Management, Lexical scoping like a fox, Of Symbol Tables and Globs, CGI to mod_perl Porting. mod_perl Coding guidelines	[reply]
Re^2: Tk: Calling Module More than Once Creates Problems by Anonymous Monk on Jul 25, 2013 at 03:19 UTC
Re^4: Border-less main window (Alt+F4 Ctrl+C, Re: Perk Tk - how to send a value from a subroutine back to the main program using Button (without MainLoop),Re: Perl tk FindNext in a text widget	[reply]
Re: Tk: Calling Module More than Once Creates Problems by Anonymous Monk on Jul 24, 2013 at 18:00 UTC
It would help to strip your code down to the bare minimum that shows the problem, and post that. From what you've said, it sounds to me like Tk has absolutely nothing to do with any of it. From your wording, it also sounds like you might be trying to use side effects of loading the module to do your calculation, rather than loading the module once and then calling a sub within it to do the calculation.	[reply]