Skip Menu |

This queue is for tickets about the Getopt-Declare CPAN distribution.

Report information
The Basics
Id: 90223
Status: new
Priority: 0/
Queue: Getopt-Declare

Owner: Nobody in particular
Requestors: t.hirsch [...]

Bug Information
Severity: Normal
Broken in: 1.14
Fixed in: (no value)

Subject: parameter values conflicting with parameter names
Download (untitled) / with headers
text/plain 881b
Let's assume that we've got 2 parameters defined in the declaration: test <test> map <map> Unfortunately there's a map called "testmap". So my command line looks like: ./ map testmap The result of Getopt::Declare's parsing however is test=map Why? That's easy: test has 4 characters and map only 3 characters. The priorization of Getopt::Declare favors longer parameters over shorter ones. How to fix that? I want to suggest to enhance Getopt::Declare with a parameter for the declaration that forces one (or more) space between the parameter name and its value. Something like: [space] Or if this feature correlates with disabling the smart parsing of squeezed parameters (I mean "-a -b == -ab") it might also be called [no-smart-parsing] Of course I also appreciate any hint of how to fix my problem with the current features of Getopt::Declare.

This service is sponsored and maintained by Best Practical Solutions and runs on infrastructure.

Please report any issues with to