>> If you are using a "require" statement, you cannot specify a path. Use the syntax "require 'libfile.pl' ; "and place the libfile.pl file in the same directory as your script.
前一句是对的,"and"开始的后半句可能有问题,实际上源文件并不一定要放在同一目录下。
Why doesn't Perl Builder step into a routine in another module or library?
If you have difficulty stepping into (or stopping at a breakpoint within) a module or library, please check the following:
The module or library must be open in the IDE before you start debugging. Perl Builder will not open the file automatically. Note that the subroutine will still be executed whether the module is open or not. However, if you want to step into it with the debugging commands, it must be open in the IDE.
Debugging must be enabled for the module. If the module has a standard Perl extension, such as .pl, .pm, etc, debugging will be enabled by default. If you are using another extension, you will need to enable debugging by opening the Module list and checking the box for the file at the bottom of the window. To open the Module List, choose View Module List from the File menu.
If you are using a "require" statement, you cannot specify a path. Use the syntax "require 'libfile.pl' ; "and place the libfile.pl file in the same directory as your script.
If you are using something like, "use xxx::yyy", Perl Builder will support up to 3 levels. You will not be able to step into something like "www::xxxx::yyyy::zzz".
Modules and their locations must be specified in your code with constructs such as "use" "require", "uselib", etc. Perl Builder does not support using command line switches for this.
If any of the above require you to modify your code, you can use the $::PERLBUILDER flag to determine whether you are running in Perl Builder and execute different code accordingly.
(1) Perl Builder maintains a project file for every main script you work with. The project file has the same name as the script, but a ".pbp" extension. The project file keeps track of various settings associated with your script. You can think of the main script as playing a similar to role "makefile, " "workspace," or "project" in other development tools.
(2) You must open the file in the IDE before running your script. If a module or library is not open in the IDE, Perl Builder will step over it when debugging.