Date: Thu, 7 Sep 2017 19:47:16 +0800 From: by <by@meetlost.com> To: Yubin Ruan <ablacktshirt@gmail.com> Cc: freebsd-hackers@freebsd.org Subject: Re: Parse command line arguments with getopt_long() Message-ID: <50555B87-1EFF-4C1D-92F0-7E98123BD2E6@meetlost.com> In-Reply-To: <CAJYFCiPfxMFRsgKfuW2e0Ph5dptvhLae2-uPFqvcd8SEnQrH0g@mail.gmail.com> References: <373D1051-950A-41B1-BB33-55540A1E393A@meetlost.com> <CAJYFCiO6XJRAuFYRYsCcwF2VnCHsDzx8Ety10GLV6gXqeWzMvQ@mail.gmail.com> <4CE43FB0-BC24-4498-9752-F4DF7F1D43F4@meetlost.com> <CAJYFCiPfxMFRsgKfuW2e0Ph5dptvhLae2-uPFqvcd8SEnQrH0g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
OK I will take a look about that. by >=20 > 2017-09-07 19:20 GMT+08:00 by <by@meetlost.com>: >> Hi, >>=20 >> What do you mean of "gflags"? >>=20 >> And I think iterate argv would be simple to implement. >>=20 >> Just considering whether it is necessary to add this into library if impl= ement it in a generic way. >=20 > gflags is a library used to parse command line arg, developed and > open-sourced by google. >=20 > Yubin >=20 >>=20 >>> Will "gflags" be OK? >>>=20 >>> Yubin >>>=20 >>=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50555B87-1EFF-4C1D-92F0-7E98123BD2E6>