<p><a href="https://github.com/ProfOak/flag2" rel="nofollow">https://github.com/ProfOak/flag2</a></p>
<p>Hey all, I made a flag library for Go. I was not satisfied with the flag library that comes with the standard library. My issue was that the flags did not follow anything I was used to. You could use full words with the single dash: <code>-flag</code>. This also prevents you from stringing multiple single character arguments in a single dash: <code>-asdf</code> meaning <code>-a -s -d -f</code>.</p>
<p>I realize my library is a little rough around the edges but I'm pretty satisfied with how it's turning out so far.</p>
<p>Readme: <a href="https://github.com/ProfOak/flag2/blob/master/README.md" rel="nofollow">https://github.com/ProfOak/flag2/blob/master/README.md</a></p>
<p>Exhaustive example: <a href="https://github.com/ProfOak/flag2/tree/master/test" rel="nofollow">https://github.com/ProfOak/flag2/tree/master/test</a></p>
<hr/>**评论：**<br/><br/>raff99: <pre><p>Given the name, I would have liked something with an interface to the "flag" package.</p>
<p>For example you could use the same interface and make the first parameter (flag name) support something like "short|long" (where short would be the one-letter flag name and long the expanded name).</p>
<p>That way one could just import "flag2" as flag and get the new behaviour.</p></pre>ProfOak_: <pre><p>That's a fair point. I hadn't considered the name implying that before, but I get what you're saying. I may change the name in the near future. I just wanted to get my code out there for more eyes to judge it.</p></pre>jtblin: <pre><p>How does that compare to <a href="https://github.com/spf13/pflag" rel="nofollow">https://github.com/spf13/pflag</a>?</p></pre>ProfOak_: <pre><p>Great question! I had not seen that before I started this project. </p>
<p>It looks like we share the same goal with traditional posix style flags. But the first thing that jumps out at me is implementation. The setup code for pflag looks more like the flag library that comes with go.</p>
<pre><code>var ip *int = flag.Int("flagname", 1234, "help message for flagname")
var flagvar int
flag.IntVar(&flagvar, "flagname", 1234, "help message for flagname")
</code></pre>
<p>My library behaves more like Python's optparse library. One of the reasons I came to like Go is because I had a lot of fun programming in it, similar to the way I felt about programming in Python.</p>
<p>The other thing is that flag2 generates a help message for the programmer to call within their code. I didn't read anything like that on the pflag readme.</p>
<p><a href="https://github.com/ProfOak/flag2/blob/master/test/test.go#L66" rel="nofollow">f.Usage()</a></p>
<p><a href="https://github.com/ProfOak/flag2/blob/master/test/README.md" rel="nofollow">How the generated text looks</a></p>
<p>optparse in python:</p>
<pre><code>from optparse import OptionParser
parser = OptionParser()
parser.add_option("-f", "--file", dest="filename",
help="write report to FILE", metavar="FILE")
parser.add_option("-q", "--quiet",
action="store_false", dest="verbose", default=True,
help="don't print status messages to stdout")
(options, args) = parser.parse_args()
</code></pre>
<p>flag2 in Go (modified version of the code on my readme):</p>
<pre><code>package main
import (
"os"
"fmt"
"github.com/ProfOak/flag2"
)
func main() {
f := flag2.NewFlag()
f.AddString("n", "name", "this flag wants a name as input", "billy")
f.AddBool("b", "bool", "this flag will store true if used", false)
options, args := f.Parse(os.Args)
}
</code></pre></pre>gavv42: <pre><p>BTW, if it's like <code>optparse</code> and you're thinking about renaming the package, you could rename it to <code>optparse</code>.</p></pre>
