forked from osmocom/wireshark
documentation: Suggest using prefixed public symbols
Change-Id: I9153756b0e921fd74d7df9d119337f5484856ba0 Reviewed-on: https://code.wireshark.org/review/15940 Reviewed-by: Anders Broman <a.broman58@gmail.com>
This commit is contained in:
parent
04058b8af3
commit
a8f73e92fd
|
@ -659,6 +659,11 @@ intercaps for functions and variable names. This is especially important if you
|
||||||
are writing code that will be called from outside your code. We are just
|
are writing code that will be called from outside your code. We are just
|
||||||
trying to keep things consistent for other developers.
|
trying to keep things consistent for other developers.
|
||||||
|
|
||||||
|
C symbols exported from libraries shipped with Wireshark should start with a
|
||||||
|
prefix that helps avoiding name collision with public symbols from other shared
|
||||||
|
libraries. The current suggested prefixes for newly added symbols are
|
||||||
|
ws_, wslua_, wmem_ and wtap_.
|
||||||
|
|
||||||
5. White space convention.
|
5. White space convention.
|
||||||
|
|
||||||
Please avoid using tab expansions different from 8 column widths, as not all
|
Please avoid using tab expansions different from 8 column widths, as not all
|
||||||
|
|
Loading…
Reference in New Issue