inconsistent naming convention

[basilkohler]

example: pkt-ccntlv-enc.c: ccnl_ccntlv_fillContentWithHdr instead of ccnl_ccntlv_fill_content_with_hdr

what should the convention be? Always a_b?

[tschudin]

On Wed, 29 Oct 2014, Basil Kohler wrote:

example: pkt-ccntlv-enc.c: ccnl_ccntlv_fillContentWithHdr instead of
ccnl_ccntlv_fill_content_with_hdr

what should the convention be? Always a_b?

No, I prefer camelcase for the functional desciption and x_y for the
categories (ccnl software, ccntlv library)

[basilkohler]

In that case there there are other incosistent names like ccnl_get_face_or_create or ccnl_populate_cache.

This is a minor issue ofcourse and i would give it a low priority if possible with the github interface.
But it is probably a good idea to make the naming consistent going forward and maybe write the naming convention down somewhere so that everyone is aware of them.