more comfortable Option parsing? (CCAN)

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Harald Welte laforge at gnumonks.org
Wed Feb 24 16:30:02 UTC 2016


FYI, Rusty's CCAN contains some interesting option parsing code released
under GPLv2+, i.e. compatible to libosmocore:
Usage is explained in
https://github.com/rustyrussell/ccan/blob/master/ccan/opt/_info

It seems rather small and simple, and permits the subsequent addition of
options, i.e. some shared code can register options, and other parts of
the code can register even more options to it (like our libraries, or
bts-specific code in osmo-bts, ...)

I have more pressing things on my todo list than convert this now, but
as there was some discussion regarding gengetopt here recently, I
thought I might point out an alternative.

We might also look into the LGPL 2.1+ CCAN htable
https://github.com/rustyrussell/ccan/blob/master/ccan/htable/_info
as a possible replacement for those areas where our linear llist
iterations should turn out to be problematic.

Regards,
	Harald
-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



More information about the OpenBSC mailing list