The sed manual clearly states that the available backreferences available for the replacement string in a substitute are numbered \1 through \9. I'm trying to parse a log file that has 10 fields.
I have the regex formed for it but the tenth match (and anything after) isn't accessible.
Does anyone have an elegant way to circumvent this limitation in KSH (or any language that perhaps I can port to shell scripting)?
Consider a solution that doesn't require the use of regular expression backreferences. For example, if you have a simple field delimiter, use
split
, or even use awk for your processing instead of perl.Split the stream with -e, as long as the replaced elements are with in the group that you split them with. When I did a date split so I could re-org the date-time into a string of 14 digits, I had to split the stream up 3 times.
20130205161449
If you have
GNU awk
, You can do things with much more in control. For this you would be needingmatch(source,/regex/,array)
construct.Example:
Sample input for test:
sed
works fine till\9
:sed
broke when\10
is added, it is considered is\1
+0
.awk
to rescue when any back reference added more than 9 is added. Here 10th refrence is added:Can you user
perl -pe 's/(match)(str)/$2$1/g;'
in place of sed? The way to circumvent the backreference limit is to use something other than sed.Also, I suppose you could do your substitution in two steps, but I don't know your pattern so I can't help you out with how.
You're asking for a shell script solution - that means you're not limited to using just sed, correct? Most shells support arrays, so perhaps you can parse the line into a shell array variable? If need be, you could even parse the same line multiple times, extracting different bits of information on each pass.
Would that do?