Skip to content

Commit

Permalink
exchanged ze and zc/p
Browse files Browse the repository at this point in the history
  • Loading branch information
milyin committed Oct 14, 2024
1 parent 7e50736 commit 2ae9323
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions docs/concepts.rst
Original file line number Diff line number Diff line change
Expand Up @@ -158,12 +158,12 @@ Most functions and types in the C API use the `z_` prefix, which applies to the
These functions and types are guaranteed to be available in all Zenoh implementations on C
(currently, Rust-based zenoh-c and pure C zenoh-pico).

The `zc_` prefix identifies API specific to zenoh-c, while zenoh-pico uses the `zp_` prefix for the same purpose.
E.g. zenoh-c and zenoh-pico have different approaches to configuration and therefore each have it's own set
of `zc_config_...` and `zp_config_...` functions.

The `ze_` prefix is used for the API that is not part of the core zenoh API. There is no guarantee that
these functions and types are available everywhere. However, when they are provided, they should
have the same prototype and behavior across all implementations. Typically, these are functions and types
provided by the `zenoh-ext` Rust library for zenoh-c and are not available in zenoh-pico. However, the data
serialization API is implemented in zenoh-pico with the same `ze_` prefix.

The `zc_` prefix identifies API specific to zenoh-c, while zenoh-pico uses the `zp_` prefix for the same purpose.
E.g. zenoh-c and zenoh-pico have different approaches to configuration and therefore each have it's own set
of `zc_config_...` and `zp_config_...` functions.
serialization API is implemented in zenoh-pico with the same `ze_` prefix.

0 comments on commit 2ae9323

Please sign in to comment.