This won't compile
var ExtRegex =
regexp.MustCompile("(M|m)(p|P)(3|4))|((F|f)(L|l)(A|a)(C|c))$")
with a
./prog.go:10:18:
regexp.MustCompile("((M|m)(p|P)(3|4))|((F|f)(L|l)(A|a)(C|c))$") (value of
type *regexp.Regexp) is not constant
while
const pat = "((M|m)(p|P)(3|4))|((F|f)(L|l)(A|a)(C|c))$"
var ExtRegex = regexp.MustCompile(pat)
Works fine.
So, why can't the regexp be a constant?
Is there some state that is kept in the regexp.Regexp store?
And perhaps more importantly, what is the proper go style to
have a compiled regexp?
I could put the var statement outside all blocks, so its in effect
a package variable. But I think having package variable is bad form.
I'm using the regexp in a loop for all the strings in all the files in a
directory tree.
I really don't want to compile them for ever pass thru the lines
Thanks
Pat
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/golang-nuts/39ae6e9f-1c27-45cd-93c2-39a3b75cc6a3n%40googlegroups.com.
