Add BACKWARD COMPATIBILITY for more post-1.0 APIs.

[skip ci]

diff --git a/pcap_datalink_val_to_name.3pcap b/pcap_datalink_val_to_name.3pcap
index 119e8b0528c97622d8560a8ae18d2db51a345788..bbfa3f80c7e76d39cd1eaf6d29777d6919f42e28 100644 (file)
--- a/pcap_datalink_val_to_name.3pcap
+++ b/pcap_datalink_val_to_name.3pcap
@@ -63,5 +63,14 @@ If the type value does not correspond to a known
 .B DLT_
 value, the string "DLT n" is returned, where n is the value of
 the dlt argument.
+.SH BACKWARD COMPATIBILITY
+The
+.BR pcap_datalink_val_to_description_or_dlt ()
+function first became available in libpcap release 1.10.0.  In previous
+releases,
+.BR pcap_datalink_val_to_description ()
+would have to be called and, if it returned
+.BR NULL ,
+a default string would have to be constructed.
 .SH SEE ALSO
 .BR pcap (3PCAP)

diff --git a/pcap_dump_ftell.3pcap b/pcap_dump_ftell.3pcap
index 58df7a4461ecb3382a99db9b9e99796eaefc599c..062d60957a9f8fa12b37c45b51cbd108f644c854 100644 (file)
--- a/pcap_dump_ftell.3pcap
+++ b/pcap_dump_ftell.3pcap
@@ -54,5 +54,11 @@ but that fit in a
 are supported, this will return the file offset without truncation.
 .B PCAP_ERROR
 is returned on error.
+.SH BACKWARD COMPATIBILITY
+The function
+.BR pcap_dump_ftell64 ()
+became available in libpcap release 1.9.0.  In previous releases, there
+was no mechanism to obtain a file offset that is too large to fit in a
+.BR long .
 .SH SEE ALSO
 .BR pcap (3PCAP)

diff --git a/pcap_get_required_select_timeout.3pcap b/pcap_get_required_select_timeout.3pcap
index e70bc02a40c04bc781fb5935689c935e9a4b739b..0256a6a5e2f80133789b4fe6f082acbabaf7c9e1 100644 (file)
--- a/pcap_get_required_select_timeout.3pcap
+++ b/pcap_get_required_select_timeout.3pcap
@@ -160,6 +160,16 @@ should be changed to call it for each call to
 or
 .BR kevent ()
 even if the code must also work with libpcap 1.9.x.
+.SH BACKWARD COMPATIBILITY
+This function became available in libpcap release 1.9.0.  In previous
+releases,
+.BR select (),
+.BR poll (),
+.BR epoll_wait (),
+and
+.BR kevent ()
+could not be used for devices that don't provide a selectable file
+descriptor.
 .SH SEE ALSO
 .BR pcap (3PCAP),
 .BR pcap_get_selectable_fd (3PCAP),

diff --git a/pcap_init.3pcap b/pcap_init.3pcap
index ba34cc4500b0e8ce80ad5d904e33950143b13a37..543f08331dc5bdda7c0403bedf52dd4fca90dcad 100644 (file)
--- a/pcap_init.3pcap
+++ b/pcap_init.3pcap
@@ -91,5 +91,9 @@ is filled in with an appropriate error message.
 is assumed to be able to hold at least
 .B PCAP_ERRBUF_SIZE
 chars.
+.SH BACKWARD COMPATIBILITY
+This function became available in libpcap release 1.10.0.  In previous
+releases, on Windows, all strings supplied as arguments, and all strings
+returned to the caller, are in the local character encoding.
 .SH SEE ALSO
 .BR pcap (3PCAP)

diff --git a/pcap_open_dead.3pcap.in b/pcap_open_dead.3pcap.in
index e28d5bda75025d4e19b00fec71c0f28ed7a7f40b..ced7d6cf1c3e353fa9e70f3d5484f3b57ffa5a2b 100644 (file)
--- a/pcap_open_dead.3pcap.in
+++ b/pcap_open_dead.3pcap.in
@@ -74,6 +74,12 @@ seconds and microseconds, and
 should be specified if the packets to be written have time stamps in
 seconds and nanoseconds.  Its value does not affect
 .BR pcap_compile (3PCAP).
+.SH BACKWARD COMPATIBILITY
+The
+.BR pcap_open_dead_with_tstamp_precision ()
+function became available in libpcap release 1.5.1.  In previous
+releases, there was no mechanism to open a savefile for writing with
+time stamps given in seconds and nanoseconds.
 .SH SEE ALSO
 .BR pcap (3PCAP),
 .BR \%pcap-linktype (@MAN_MISC_INFO@)