Hello, Since glog's readme recommends firing off an email to golang-nuts to report possible issues, here I go.
I really like the idea of specifying flags in flagfiles and environment variables. This Go package seems to let me do that, while staying pretty much API-compatible with the standard flag package: github.com/namsral/flag However, if I start using it as a replacement for "flag" package, the program (naturally) only recognizes flags specified using namsral's flag package. This means that the flags defined in the glog package are not visible to namsral's package, and thus are not visible to the user. Since variables backing the glog flags are not part of the public interface, I can't, really, write a nice wrapper. Instead I could write a wrapper that reads the values from namsral/flags-created variables, and uses flag.Set() to set them into Go's flag package, and then calls Go's flag.Parse(). That feels bad. Does anyone have any suggestions on alternative approaches? Could the variables backing the flags be exposed, so I can do my own calls to flag.BoolVar()/flag.Var()? Would it make sense to extend Go's flag package to use the environment and flagfiles in addition to just command line arguments? -- 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 golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
