| /freebsd-12.1/contrib/ntp/libjsmn/ |
| H A D | README.md | 5 jsmn (pronounced like 'jasmine') is a minimalistic JSON parser in C. It can be 8 You can find more information about JSON format at [json.org][1] 18 Most JSON parsers offer you a bunch of functions to load JSON data, parse it 20 every JSON packet or allocating temporary objects to store parsed JSON fields 23 JSON format itself is extremely simple, so why should we complicate it? 125 to simplify string extraction from JSON data. 134 // js - pointer to JSON string 150 * `JSMN_ERROR_INVAL` - bad token, JSON string is corrupted 151 * `JSMN_ERROR_NOMEM` - not enough tokens, JSON string is too large 152 * `JSMN_ERROR_PART` - JSON string is too short, expecting more JSON data [all …]
|
| /freebsd-12.1/lib/libpmc/pmu-events/arch/powerpc/ |
| H A D | mapfile.csv | 2 # PVR,Version,JSON/file/pathname,Type 6 # Version could be used to track version of of JSON file 8 # JSON/file/pathname is the path to JSON file, relative 12 # Multiple PVRs could map to a single JSON file.
|
| /freebsd-12.1/lib/libpmc/pmu-events/arch/arm64/ |
| H A D | mapfile.csv | 2 # MIDR,Version,JSON/file/pathname,Type 7 # Version could be used to track version of of JSON file 9 # JSON/file/pathname is the path to JSON file, relative
|
| /freebsd-12.1/lib/libpmc/pmu-events/ |
| H A D | README | 8 The 'jevents' program tries to locate and process JSON files in the directory 12 JSON files, each of which describes a set of PMU events. 19 - To reduce JSON event duplication per architecture, platform JSONs may 27 should be placed in a separate JSON file - where the file name identifies 30 All the topic JSON files for a CPU model/family should be in a separate 41 Using the JSON files and the mapfile, 'jevents' generates the C source file, 45 (one table like the following, per JSON file; table name 'pme_power8' 46 is derived from JSON file name, 'power8.json'). 80 JSON file. Hence several entries in the pmu_events_map[] could map 137 is the pathname to the directory containing the CPU's JSON [all …]
|
| /freebsd-12.1/contrib/libxo/doc/ |
| H A D | formatting.rst | 14 Modern tool developers favor encoding schemes like XML and JSON, 25 traditional text output, as well as XML and JSON formatted data. HTML 38 JSON: 61 - JSON output can be used for RESTful APIs and integration with 66 In general, XML and JSON are suitable for encoding data, while TEXT is 86 using a single code path to make TEXT, XML, JSON or HTML, deciding at 95 call, but also has enough information to generate XML, JSON, and HTML. 123 JSON Output 126 JSON output consists of a hierarchical set of objects and lists, each
|
| H A D | xo.rst | 8 the libxo library. Using `xo`, shell scripts can emit XML, JSON, and 12 XML, "-J" for JSON, "-H" for HTML, or "-T" for TEXT, which is the 29 JSON: 57 JSON: 86 JSON: 103 --json OR -J Generate JSON output
|
| H A D | field-modifiers.rst | 17 e encoding Only emit for encoding styles (XML/JSON) 25 n no-quotes Do not quote the field when using JSON style 27 q quotes Quote the field when using JSON style 38 and that the value should be quoted when encoded for JSON. 56 JSON: 240 JSON: 254 the quoting of values in the JSON output style. JSON uses quotes for 262 JSON: 302 the quoting of values in the JSON output style. JSON uses quotes for 309 JSON: [all …]
|
| H A D | options.rst | 47 json Emit JSON output 54 no-top Do not emit a top set of braces (JSON) 55 not-first Pretend the 1st output item was not 1st (JSON) 59 underscores Replace XML-friendly "-"s with JSON friendly "_"s 84 - "underscores" can be used with JSON output to change XML-friendly 85 names with dashes into JSON-friendly name with underscores. 105 J Enable JSON output (XO_STYLE_JSON) 111 u Change "-"s to "_"s in element names (JSON)
|
| H A D | index.rst | 13 libxo - A Library for Generating Text, XML, JSON, and HTML Output 16 The libxo library allows an application to generate text, XML, JSON,
|
| H A D | libxo.txt | 302 JSON: 775 JSON: 913 JSON: 929 JSON: 963 JSON: 978 JSON: 1175 JSON: 1315 JSON: 2588 JSON: 2616 JSON: [all …]
|
| H A D | field-formatting.rst | 119 JSON, and HTML styles) or locale-based strings for display in text 166 current locale (as described above), while XML, JSON, and HTML use 187 ignored for the JSON and XML styles. For HTML, these characters are 196 JSON: 226 for JSON and XML. If not provided, it defaults to the primary format 352 JSON:
|
| H A D | intro.rst | 5 The libxo library allows an application to generate text, XML, JSON, 67 You want to support features like XML, JSON, and HTML rendering to
|
| H A D | howto.rst | 62 footprint of the library for smaller installations. XML, JSON, and 139 "count" and "event" are used as names for JSON and XML output. The 182 Text output doesn't have any sort of hierarchy, but XML and JSON 349 native language support, as well as libxo's normal XML, JSON, and HTML
|
| H A D | api.rst | 163 XO_STYLE_JSON JSON encoded data 167 The "XML", "JSON", and "HTML" output styles all use the UTF-8 289 XML, JSON, and HTML output. Text output is not affected. 622 For XML and JSON, individual fields appear inside hierarchies which 633 JSON encodes lists using a single name and square brackets:: 715 JSON: 755 generation of XML and JSON data. 859 JSON: 1035 as part of the data for encoding styles (XML and JSON). This 1220 puts the error into XML or JSON elements:: [all …]
|
| H A D | format-strings.rst | 39 ("<in-stock>65</in-stock>"), JSON ('"in-stock": 6'), or HTML (too
|
| H A D | field-roles.rst | 263 interesting for the non-display output styles (XML and JSON). Value 268 second one is used for encoding styles (XML and JSON). If no second
|
| /freebsd-12.1/contrib/llvm/lib/Support/ |
| H A D | JSON.cpp | 206 Parser(StringRef JSON) in Parser() argument 207 : Start(JSON.begin()), P(JSON.begin()), End(JSON.end()) {} in Parser() 511 Expected<Value> parse(StringRef JSON) { in parse() argument 512 Parser P(JSON); in parse()
|
| /freebsd-12.1/contrib/libxo/ |
| H A D | README.md | 4 libxo - A Library for Generating Text, XML, JSON, and HTML Output 6 The libxo library allows an application to generate text, XML, JSON,
|
| /freebsd-12.1/contrib/libucl/ |
| H A D | README.md | 36 system. However, UCL is fully compatible with `JSON` format and is able to parse json files. 63 * or in JSON: 340 * `JSON` - canonic json notation (with spaces indented structure); 341 * `Compacted JSON` - compact json notation (without spaces or newlines); 347 …n objects. Of course, a schema definition can be in UCL format instead of JSON that simplifies sch… 382 JSON language and therefore can be used as a simple JSON parser. Macro logic provides an ability to…
|
| /freebsd-12.1/contrib/libucl/lua/ |
| H A D | libucl.rockspec.in | 13 However, UCL is fully compatible with JSON format and is able
|
| /freebsd-12.1/contrib/libxo/packaging/ |
| H A D | libxo.spec.in | 18 Welcome to libxo, a library that generates text, XML, JSON, and HTML
|
| /freebsd-12.1/contrib/llvm/tools/lld/docs/ |
| H A D | make.bat | 25 echo. json to make JSON files 83 echo.Build finished; now you can process the JSON files.
|
| /freebsd-12.1/lib/clang/libllvmminimal/ |
| H A D | Makefile | 27 SRCS+= Support/JSON.cpp
|
| /freebsd-12.1/contrib/mandoc/ |
| H A D | lib.in | 86 LINE("libmj", "Minimalist JSON library (libmj, \\-lmj)") 137 LINE("libxo", "Text, XML, JSON, and HTML Output Emission Library (libxo, \\-lxo)")
|
| /freebsd-12.1/contrib/libucl/doc/ |
| H A D | api.md | 55 - `JSON` - valid json format (can possibly lose some original data, such as implicit arrays) 250 - formatted json: `UCL_EMIT_JSON` - pretty formatted JSON with newlines and spaces 366 - `UCL_STRING_ESCAPE` - perform JSON escape
|