summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
authorUwe Hermann <uwe@hermann-uwe.de>2013-05-03 14:31:11 +0200
committerUwe Hermann <uwe@hermann-uwe.de>2013-05-03 20:36:28 +0200
commitf11e9498c83d4b27ffc1029f6dbd7ef871953aca (patch)
tree705062948974a4e1888640a93a95c2f65d30261f /HACKING
parent0a7ae201ca82293fe3bb413cdddf7bcf9b0f42da (diff)
downloadlibsigrokdecode-f11e9498c83d4b27ffc1029f6dbd7ef871953aca.tar.gz
libsigrokdecode-f11e9498c83d4b27ffc1029f6dbd7ef871953aca.zip
HACKING: Document the @since Doxygen tag.
Diffstat (limited to 'HACKING')
-rw-r--r--HACKING16
1 files changed, 16 insertions, 0 deletions
diff --git a/HACKING b/HACKING
index dc4d53d..82176e1 100644
--- a/HACKING
+++ b/HACKING
@@ -90,6 +90,22 @@ Doxygen
/** @endcond */, so that Doxygen doesn't include them in the output.
Variables that are "static" don't need to be marked like this.
+ - Mark all public API functions (SRD_API) with a @since tag which indicates
+ in which release the respective function was added. If the function has
+ existed before, but its API changed later, document this as well.
+
+ Non-public functions (static ones, and those marked SRD_PRIV) don't need
+ to have @since markers.
+
+ The @since tag should be the last one, i.e. it should come after @param,
+ @return, @see, and so on.
+
+ Examples:
+
+ @since 0.1.0
+
+ @since 0.1.1 (but the API changed in 0.2.0)
+
Protocol decoder guidelines
---------------------------