in reply to How best to oganize this perl code

This depends on what actual code is in b.pl, and what a.pl needs it for. Does a.pl just call it because it performs some function that a would otherwise have to duplicate, or does it also need b to do some user interaction?

IE. Can you abstract what b does into a module, that both could call? If so, do that. If b is a standalone exe that a just happens to need, then call the exe, if that is what you are delivering.

C.

Replies are listed 'Best First'.
Re^2: How best to oganize this perl code
by richz (Beadle) on Sep 09, 2004 at 13:19 UTC
    C, Your idea is what I ended up deciding on. Like you figured, I did not want to duplicate the function that b.pl was providing in a.pl. I decided on making b.pl a module for this reason; the downside since I am compiling these into executables is that if I enhance or modify b.pl I will have to compile a.pl into a.exe again... Thanks.
[reply]

In Section Seekers of Perl Wisdom