Re: naming contest: gsm_network, gsm_subscriber_connection

On Fri, Nov 11, 2016 at 02:58:07PM +0100, Harald Welte wrote:

In general we shouldn't call structures how we are (or might be) calling functional elements. So if it's a msc or bsc instance or context, postfix it by _inst, _instance, _ctx or _context.

Also, the osmo_ naming prefix makex mostly sense in the conext of library code to avoid namespace pollution. I think I actually like it if application code structures and symbols do not have osmo_ prefixes.

...

--> bsc_subscr_conn / msc_subscr_conn I like these best; but add osmo? +1

fine with me.

So for now my finalists are: gsm_network --> bsc_ctx / msc_ctx and gsm_subscriber_connection --> bsc_subscr_conn / msc_subscr_conn

Speak now or forever hold your peace...

~N