Re^2: mapping dynamic fields to options

in reply to Re: mapping dynamic fields to options
in thread mapping dynamic fields to options

I *could* segregate them which would immediately solve my problem, it just comes at the cost of readability and usability, unless I'm misunderstanding you.

I feel like just general use of this will be challenging enough without introducing additional (hopefully unnecessary) hardships.

Comment on Re^2: mapping dynamic fields to options

Replies are listed 'Best First'.
Re^3: mapping dynamic fields to options by NetWallah (Canon) on Oct 22, 2012 at 06:02 UTC
Apologies for not being clear - what I meant was you could segregate THINKING about the problem, and use both those modules in a single program. GetOptions would process the option list, and Template would do the substitution. From the looks of your requirements, the program implementing this would be quite small, and completely flexible. "By three methods we may learn wisdom: First, by reflection, which is noblest; Second, by imitation, which is easiest; and third by experience, which is the bitterest." -Confucius	[reply]

Replies are listed 'Best First'.

Re^3: mapping dynamic fields to options
by NetWallah (Canon) on Oct 22, 2012 at 06:02 UTC

GetOptions would process the option list, and Template would do the substitution.

From the looks of your requirements, the program implementing this would be quite small, and completely flexible.

"By three methods we may learn wisdom: First, by reflection, which is noblest; Second, by imitation, which is easiest; and third by experience, which is the bitterest." -Confucius

[reply]

In Section Seekers of Perl Wisdom