blob: 14eb110fc58c0368a98389379a4e1305d035e9cf [file] [log] [blame]
Radek Krejci5aeea3a2018-09-05 13:29:36 +02001/**
2 * @file libyang.h
3 * @author Radek Krejci <rkrejci@cesnet.cz>
4 * @brief The main libyang public header.
5 *
6 * Copyright (c) 2015 - 2018 CESNET, z.s.p.o.
7 *
8 * This source code is licensed under BSD 3-Clause License (the "License").
9 * You may not use this file except in compliance with the License.
10 * You may obtain a copy of the License at
11 *
12 * https://opensource.org/licenses/BSD-3-Clause
13 */
14
15#ifndef LY_LIBYANG_H_
16#define LY_LIBYANG_H_
17
Radek Krejci0af5f5d2018-09-07 15:00:30 +020018#include <stdint.h>
19
Radek Krejci5aeea3a2018-09-05 13:29:36 +020020#ifdef __cplusplus
21extern "C" {
22#endif
23
Radek Krejcica376bd2020-06-11 16:04:06 +020024#include "context.h"
25#include "dict.h"
Radek Krejci6caa6ab2018-10-24 10:04:48 +020026#include "log.h"
Radek Krejcif0e1ba52020-05-22 15:14:35 +020027#include "parser.h"
Radek Krejci7931b192020-06-25 17:05:03 +020028#include "parser_data.h"
Radek Krejcif0e1ba52020-05-22 15:14:35 +020029#include "parser_schema.h"
30#include "plugins_types.h"
31#include "printer.h"
32#include "printer_data.h"
33#include "printer_schema.h"
Radek Krejci6caa6ab2018-10-24 10:04:48 +020034#include "set.h"
Radek Krejcie7b95092019-05-15 11:03:07 +020035#include "tree.h"
36#include "tree_data.h"
Radek Krejci6caa6ab2018-10-24 10:04:48 +020037#include "tree_schema.h"
38
Radek Krejci5aeea3a2018-09-05 13:29:36 +020039/**
Radek Krejcie53a8dc2018-10-17 12:52:40 +020040 * @mainpage About
41 *
42 * libyang is a library implementing processing of the YANG schemas and data modeled by the YANG language. The
43 * library is implemented in C for GNU/Linux and provides C API.
44 *
45 * @section about-features Main Features
46 *
47 * - [Parsing (and validating) schemas](@ref howtoschemasparsers) in YANG format.
48 * - [Parsing (and validating) schemas](@ref howtoschemasparsers) in YIN format.
49 * - [Parsing, validating and printing instance data](@ref howtodata) in XML format.
50 * - [Parsing, validating and printing instance data](@ref howtodata) in JSON format
51 * ([RFC 7951](https://tools.ietf.org/html/rfc7951)).
52 * - [Manipulation with the instance data](@ref howtodatamanipulators).
53 * - Support for [default values in the instance data](@ref howtodatawd) ([RFC 6243](https://tools.ietf.org/html/rfc6243)).
54 * - Support for [YANG extensions and user types](@ref howtoschemaplugins).
55 * - Support for [YANG Metadata](@ref howtoschemametadata) ([RFC 7952](https://tools.ietf.org/html/rfc6243)).
56 *
57 * The current implementation covers YANG 1.0 ([RFC 6020](https://tools.ietf.org/html/rfc6020)) as well as
58 * YANG 1.1 ([RFC 7950](https://tools.ietf.org/html/rfc7950)).
59 *
60 * @section about-license License
61 *
62 * Copyright (c) 2015-2017 CESNET, z.s.p.o.
63 *
64 * (The BSD 3-Clause License)
65 *
66 * Redistribution and use in source and binary forms, with or without
67 * modification, are permitted provided that the following conditions
68 * are met:
69 * 1. Redistributions of source code must retain the above copyright
70 * notice, this list of conditions and the following disclaimer.
71 * 2. Redistributions in binary form must reproduce the above copyright
72 * notice, this list of conditions and the following disclaimer in
73 * the documentation and/or other materials provided with the
74 * distribution.
75 * 3. Neither the name of the Company nor the names of its contributors
76 * may be used to endorse or promote products derived from this
77 * software without specific prior written permission.
78 */
79
80/**
Radek Krejci52785a22019-09-11 12:57:26 +020081 * @page howto libyang API Overview
Radek Krejcie53a8dc2018-10-17 12:52:40 +020082 *
83 * - @subpage howtocontext
84 * - @subpage howtoschemas
85 * - @subpage howtodata
86 * - @subpage howtoxpath
87 * - @subpage howtoxml
88 * - @subpage howtothreads
89 * - @subpage howtologger
Radek Krejci290a6a52019-09-12 17:13:17 +020090 * - @subpage howtoplugins
Radek Krejcie53a8dc2018-10-17 12:52:40 +020091 * - @subpage howtostructures
92 */
93
94/**
Radek Krejci290a6a52019-09-12 17:13:17 +020095 * @internal
96 * @page internals Developers' Notes
97 * @tableofcontents
98 *
99 * Following texts describes various internal subsystems and mechanism in libyang which are hidden from external users, but important
100 * for libyang developers. The texts should explain various decisions made and internal processes utilized in libyang.
101 */
102
103/**
Radek Krejcie53a8dc2018-10-17 12:52:40 +0200104 * @page howtostructures Data Structures
105 *
106 * @section sizedarrays Sized Arrays
107 *
108 * The structure starts with 32bit number storing size of the array - the number of the items inside. The size is part of the
Radek Krejci2c4e7172018-10-19 15:56:26 +0200109 * array to have it allocated together with the array itself only when it is needed. However, the pointers to the array always
110 * points after the 32b number, so items can be accessed directly as for standard C arrays. Because of a known size (available
111 * via ::LY_ARRAY_SIZE macro), it is not terminated by any special byte (sequence), so there is also no limitation for specific
112 * content of the stored records (e.g. that first byte must not be NULL).
Radek Krejcie53a8dc2018-10-17 12:52:40 +0200113 *
Radek Krejci2c4e7172018-10-19 15:56:26 +0200114 * The sized arrays must be carefully freed (which should be done anyway only internally), since pointers to the sized arrays used
115 * in libyang structures, does not point to the beginning of the allocated space.
Radek Krejcie53a8dc2018-10-17 12:52:40 +0200116 *
117 * - ::LY_ARRAY_SIZE
Radek Krejcie53a8dc2018-10-17 12:52:40 +0200118 * - ::LY_ARRAY_FOR
119 *
120 * @section struct_lists Lists
121 *
122 * The lists are structures connected via a `next` pointer. Iterating over the siblings can be simply done by ::LY_LIST_FOR macro.
123 */
124
Radek Krejci950f6a52019-09-12 17:15:32 +0200125/**
126 * @page howtoplugins Plugins
127 *
128 * libyang supports several types of plugins to better support generic features of YANG that need some specific code for
129 * their specific instances in YANG schemas. This is the case of YANG types, which are derived from YANG built-in types
130 * (which are implemented by libyang), but the description of the derived type can specify some additional requirements or
131 * restriction that cannot be implemented generically and some special code is needed. The second case for libyang plugins
132 * are YANG extensions. For YANG extensions, most of the specification stays in their description (e.g. allowed substatements
133 * or place of the extension instanciation) and libyang is not able to process such a text in a generic way. In both cases,
134 * libyang provides API to provide functionality implementing the specifics of each type or extension.
135 */
Radek Krejci0af5f5d2018-09-07 15:00:30 +0200136#ifdef __cplusplus
137}
138#endif
Radek Krejci5aeea3a2018-09-05 13:29:36 +0200139
140#endif /* LY_LIBYANG_H_ */