Lines Matching +refs:include +refs:file

11 If you add a new public function or macro to a header file without documenting
15 include/openssl/bio.h: macro BIO_set_dgram_origin(3) undocumented
16 include/openssl/bio.h: macro BIO_get_dgram_origin(3) undocumented
17 include/openssl/bio.h: macro BIO_set_dgram_dest(3) undocumented
18 include/openssl/bio.h: macro BIO_get_dgram_dest(3) undocumented
23 So, create a new `.pod` file named `doc/man3/FUNCTION.pod`.
25 If you are asked to document several related functions in that file,
26 you can create a single pod file in which you document them together.
27 In this case, use the name of the first function as the file name,
37 Next, you need to add your new file to the `doc/build.info` file.
57 to edit the file `util/other.syms` to add the names of your `#define`
59 This file gets sorted alphabetically prior to each major release,
60 but new additions should be placed at the end of the file.
88 diff --git a/include/openssl/bio.h.in b/include/openssl/bio.h.in
90 --- a/include/openssl/bio.h.in
91 +++ b/include/openssl/bio.h.in
111 include/openssl/bio.h: macro BIO_set_dgram_bar(3) undocumented
130 [module definition file] of the Windows DLL, which is the
133 [module definition file]: https://docs.microsoft.com/en-us/cpp/build/exporting-from-a-dll-using-def…
166 include/openssl/bio.h: macro BIO_set_dgram_bar(3) undocumented
174 can be utilized to check for this. A completely new documentation file