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

Report information
The Basics

Nobody in particular
vkavalov [...]

(no value)
Broken in:
(no value)
Fixed in:
(no value)

CC: vesselin kavalov <>
Subject: How can I add to an existing ticket?
Date: Thu, 23 Sep 2010 16:30:34 -0700
From: vesselin kavalov <>
Hi Kevin, I have a ? and a suggestion on how to resolve my issue closely (almost identical ;) related to RT 61310. I don't want to flood you with RTs if I can piggy-back on an existing one! Anyway, issue with repeatable arguments: I need more than one of them (as well) and tried to constrain it as: =item -f <file>... File(s) containing a list of directories to summarize, one per line. =for Euclid: repeatable file.type: readable, file =~ /^[^-]/ meaning "Stop reading arguments if the next one starts with '-' which means it is another option, not an argument to the current one". This is kinda lame, since an argument may start possibly with '-' (weird case ?!?!?) so, can it be made such that the repeatable list is auto-terminated if the next item is a registered option, since you already know all the options anyway? Thanx! vess
Noted. I am afraid of this conflicting with #34206. Given that Getopt::Euclid currently concatenates @ARGV and processes all the arguments with regular expressions, your solution may cause issues. Currently, I'm working on a major rewrite of Getopt::Euclid's argument parser that tries to fit things in based upon specificity; basically, each argument is composed of flags and placeholders, flags are more specific than placeholders, and when evaluating an argument that is ambiguous, the new parser will put that into the most specific case it can. Anyway, since this is basically a duplicate, I'll mark it resolved and I'll update the main ticket when that is done.
CC: vesselin kavalov <>
Subject: Re: [ #61600] Resolved: How can I add to an existing ticket?
Date: Thu, 23 Sep 2010 17:40:07 -0700
From: vesselin kavalov <>
Hi Kevin, thanx for the fast reply! I don't see how the two issues are related! Yes, I did try the anchors (to make sure that what I am matching is the whole string and nothing but the string)and yes, it didn't work but with a little bit of experimenting I figured out that whatever the underlaying parsing method is, it acts as if the regex is ^regex$ anchored and it's good enough for me. Anyway, if you'll re-writing the parser it's a mute point to talk about my problem now. Can't wait to try the latest version! vess On Sep 23, 2010, at 5:01 PM, Kevin Galinsky via RT wrote:
Show quoted text
> <URL: > > > According to our records, your request has been resolved. If you have any > further questions or concerns, please respond to this message.

This service runs on Request Tracker, is sponsored by The Perl Foundation, and maintained by Best Practical Solutions.

Please report any issues with to