Re: Parsing arguments

This is usually a lot trickier than the example code you have here for reasons such as:

bareword='quoted\'s string'
bareword='quoted''s string'
bareword="quoted \"string\""
[download]

I'm not sure if that's something you're going to have to deal with, but it's always good to have a complete test case.

Comment on Re: Parsing arguments Download Code

Replies are listed 'Best First'.
Re: Re: Parsing arguments by hv (Prior) on Feb 20, 2003 at 17:42 UTC
Agreed, though there's no current requirement to support escaping in the quoted strings. But that's exactly the sort of reason I'm unhappy about the duplicated regexp chunks, since it'd be easy to enhance one of the `' ([^']) '` fragments and miss the other. Similarly, I could collapse the single- and double-quoted string checks with a style like `(["']) (.?) \1`, but that can make tracking the capture numbers even harder, since now a change in the regexp would mean updating the numbering elsewhere in the pattern as well as in the `push @args, ...` code. Hugo	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re: Re: Parsing arguments
by hv (Prior) on Feb 20, 2003 at 17:42 UTC

Agreed, though there's no current requirement to support escaping in the quoted strings. But that's exactly the sort of reason I'm unhappy about the duplicated regexp chunks, since it'd be easy to enhance one of the ' ([^']*) ' fragments and miss the other.

Similarly, I could collapse the single- and double-quoted string checks with a style like (["']) (.*?) \1, but that can make tracking the capture numbers even harder, since now a change in the regexp would mean updating the numbering elsewhere in the pattern as well as in the push @args, ... code.

[reply]
[d/l]
[select]