Re: Embedding command-line arguments within source code

> Any suggestions..

If with any you really mean any, you can find Modules as configuration files interesting.

I still use it if I have a lot of arguments for a perl program or, let say, find command.

There are no rules, there are no thumbs..
Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.

Comment on Re: Embedding command-line arguments within source code Select or Download Code

Replies are listed 'Best First'.
Re^2: Embedding command-line arguments within source code by morelenmir (Beadle) on May 20, 2018 at 18:58 UTC
Many thanks guys!!! That idea of using a module to input arguments is pretty clever all on its own. I will definitely give that a shot. Generally, learning to use the command-line debugger is a pretty slow and uncomfortable process at the moment. I aimed to work through the book 'Pro Perl Debugging' by Foley and Lester, but I found it quickly became rather confusing. However I am trying to extract the key information from the first few chapters and focus on just one or too commands--'x' to show a variable's value, 'c' to jump to the next breakpoint, 's' to step into and 'n' to step over. It would be nice to be able to customize the debugger appearance--set it for more than 80 columns for instance and specify what information it gives me at each step/jump. That is probably material for a different thread though! "Aure Entuluva!" - Hurin Thalion at the Nirnaeth Arnoediad.	[reply]

Replies are listed 'Best First'.

Re^2: Embedding command-line arguments within source code
by morelenmir (Beadle) on May 20, 2018 at 18:58 UTC

Many thanks guys!!! That idea of using a module to input arguments is pretty clever all on its own. I will definitely give that a shot.

Generally, learning to use the command-line debugger is a pretty slow and uncomfortable process at the moment. I aimed to work through the book 'Pro Perl Debugging' by Foley and Lester, but I found it quickly became rather confusing. However I am trying to extract the key information from the first few chapters and focus on just one or too commands--'x' to show a variable's value, 'c' to jump to the next breakpoint, 's' to step into and 'n' to step over.

It would be nice to be able to customize the debugger appearance--set it for more than 80 columns for instance and specify what information it gives me at each step/jump. That is probably material for a different thread though!

"Aure Entuluva!" - Hurin Thalion at the Nirnaeth Arnoediad.

[reply]