@cella-lang/cfamily 0.0.0-stage → 0.1.202610300255
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGES.md +9 -0
- package/LICENSE +202 -0
- package/NOTICE +7 -0
- package/README.md +87 -2
- package/cfamily.arithmetic.cell +0 -0
- package/cfamily.behavior.cell +0 -0
- package/cfamily.cell +0 -0
- package/cfamily.clibrary.cell +0 -0
- package/cfamily.conversion.cell +0 -0
- package/cfamily.debugging.cell +0 -0
- package/cfamily.encoding.cell +0 -0
- package/cfamily.evaluation.cell +0 -0
- package/cfamily.execution.cell +0 -0
- package/cfamily.expressions.cell +0 -0
- package/cfamily.files.cell +0 -0
- package/cfamily.formatting.cell +0 -0
- package/cfamily.generate.cell +0 -0
- package/cfamily.integer.cell +0 -0
- package/cfamily.layout.cell +0 -0
- package/cfamily.librarycode.cell +0 -0
- package/cfamily.lifting.cell +0 -0
- package/cfamily.literals.cell +0 -0
- package/cfamily.memory.cell +0 -0
- package/cfamily.program.cell +0 -0
- package/cfamily.querying.cell +0 -0
- package/cfamily.representation.cell +0 -0
- package/cfamily.resolution.cell +0 -0
- package/cfamily.rules.cell +0 -0
- package/cfamily.running.cell +0 -0
- package/cfamily.scanning.cell +0 -0
- package/cfamily.sequencing.cell +0 -0
- package/cfamily.sessions.cell +0 -0
- package/cfamily.standardlibrary.cell +0 -0
- package/cfamily.state.cell +0 -0
- package/cfamily.statements.cell +0 -0
- package/cfamily.statics.cell +0 -0
- package/cfamily.summaries.cell +0 -0
- package/cfamily.syntax.cell +0 -0
- package/cfamily.syntaxcollect.cell +0 -0
- package/cfamily.syntaxnodes.cell +0 -0
- package/cfamily.syntaxtypes.cell +0 -0
- package/cfamily.syntaxwalk.cell +0 -0
- package/cfamily.tables.cell +0 -0
- package/cfamily.typed.cell +0 -0
- package/cfamily.typetext.cell +0 -0
- package/cfamily.variables.cell +0 -0
- package/index.json +10433 -0
- package/package.json +74 -3
package/CHANGES.md
ADDED
|
@@ -0,0 +1,9 @@
|
|
|
1
|
+
# @cella-lang/cfamily 的變更
|
|
2
|
+
|
|
3
|
+
## 未發佈
|
|
4
|
+
|
|
5
|
+
- 第一版:C 家族(`@cella-lang/c`、`cpp`、`arduino`)共用的深嵌入核心:語法(semorphe 送來的 JSON)、型別檢查、一份記憶體模型上的小步
|
|
6
|
+
語意、判決、除錯器的工作階段、型別查詢、把程式印回原始碼。沒有自己的入口,由三個分支使用。
|
|
7
|
+
- 判決的 `clause` 照程式的語言:C 程式引 C11,C++ 程式的核心語言規則引 C++17(N4659:有號溢位 `C++17 [expr]p4`、除以零
|
|
8
|
+
`[expr.mul]p4`、移位 `[expr.shift]p1-2`、不確定的值 `[dcl.init]p12`…);C 的標準函式庫兩者都引 C11(C++ 以引用納入)。
|
|
9
|
+
- 文字照 UTF-8:語法樹的字串、輸入、除錯時補的輸入是 Unicode 碼位,程式看到的是 UTF-8 位元組;輸出照 UTF-8 解回,不合法的序列是 U+FFFD。
|
package/LICENSE
ADDED
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
|
153
|
+
|
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
|
159
|
+
incidental, or consequential damages of any character arising as a
|
|
160
|
+
result of this License or out of the use or inability to use the
|
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
+
other commercial damages or losses), even if such Contributor
|
|
164
|
+
has been advised of the possibility of such damages.
|
|
165
|
+
|
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
+
or other liability obligations and/or rights consistent with this
|
|
170
|
+
License. However, in accepting such obligations, You may act only
|
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
+
of your accepting any such warranty or additional liability.
|
|
176
|
+
|
|
177
|
+
END OF TERMS AND CONDITIONS
|
|
178
|
+
|
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
+
|
|
181
|
+
To apply the Apache License to your work, attach the following
|
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
+
replaced with your own identifying information. (Don't include
|
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
+
comment syntax for the file format. We also recommend that a
|
|
186
|
+
file or class name and description of purpose be included on the
|
|
187
|
+
same "printed page" as the copyright notice for easier
|
|
188
|
+
identification within third-party archives.
|
|
189
|
+
|
|
190
|
+
Copyright [yyyy] [name of copyright owner]
|
|
191
|
+
|
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
+
you may not use this file except in compliance with the License.
|
|
194
|
+
You may obtain a copy of the License at
|
|
195
|
+
|
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
+
|
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
+
See the License for the specific language governing permissions and
|
|
202
|
+
limitations under the License.
|
package/NOTICE
ADDED
package/README.md
CHANGED
|
@@ -1,3 +1,88 @@
|
|
|
1
|
-
#
|
|
1
|
+
# @cella-lang/cfamily
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
The C family's core for the [Cella](https://www.npmjs.com/package/cella-lang) proof checker, as a compiled module pack:
|
|
4
|
+
C11 and C++17 as a deep embedding. A program is a data value (the JSON of its syntax tree), and its type checking and
|
|
5
|
+
execution are ordinary functions on that value.
|
|
6
|
+
|
|
7
|
+
The core has no entries of its own. Use one of its three branches, each a package with its own verdict, type query and
|
|
8
|
+
debugger; a branch lists this package in its `index.json` and loads it first.
|
|
9
|
+
|
|
10
|
+
| Package | Programs |
|
|
11
|
+
|---|---|
|
|
12
|
+
| `@cella-lang/c` | C11 (`"lang": {"k": "langC"}`) |
|
|
13
|
+
| `@cella-lang/cpp` | C++17 (`"lang": {"k": "langCpp"}`), without a board |
|
|
14
|
+
| `@cella-lang/arduino` | C++17 on an Arduino board (`"board": "uno"`, `"esp32"`, …) |
|
|
15
|
+
|
|
16
|
+
The packages depend on each other as `machine` <- `cfamily` <- `c`, `cpp` <- `arduino`.
|
|
17
|
+
|
|
18
|
+
## Programs
|
|
19
|
+
|
|
20
|
+
A program is the JSON of `cfamily.syntax`: `{"k": "prog", "n": "<node>", "lang": …, "items": […]}`, with `"board"` and
|
|
21
|
+
the host's inputs over time (`"inputs"`) for a board. Every constructor carries the node label of the editor that made
|
|
22
|
+
it (`"n"`), and a verdict, a stop of the debugger or a type error names the node.
|
|
23
|
+
|
|
24
|
+
Text is Unicode on the host's side and UTF-8 bytes in the program, as with clang and gcc: string literals, the input and
|
|
25
|
+
the debugger's fed input are encoded (`"é"` is two bytes, `sizeof("é")` is 3); the output is the bytes the program
|
|
26
|
+
wrote, decoded, with U+FFFD for an invalid sequence.
|
|
27
|
+
|
|
28
|
+
## Verdicts
|
|
29
|
+
|
|
30
|
+
A branch's `verdict src input fuel` returns:
|
|
31
|
+
|
|
32
|
+
```json
|
|
33
|
+
{"verdict": "reject", "basis": "computed", "exit": null, "out": "",
|
|
34
|
+
"problems": [{"kind": "ubOverflow", "at": "<node>", "clause": "C++17 [expr]p4", "reason": "signed overflow"}]}
|
|
35
|
+
```
|
|
36
|
+
|
|
37
|
+
- `verdict`: `accept`; `reject` (a type error, or undefined behavior); `unknown` (the standard allows results that
|
|
38
|
+
change the output, a construct the model does not have yet, or the step limit); or `invalid` (the JSON is not a
|
|
39
|
+
program, or not one for this branch: a C program for a board, a C++ program sent to `c`).
|
|
40
|
+
- `basis`: `computed` when the verdict comes from running the semantics, `kernel` when both kernels proved it
|
|
41
|
+
(`kernel_verdict_in` in `cella-lang`, with the branch's verdict: `kernel_verdict_in("cpp", "cpp.verdict", …)`).
|
|
42
|
+
- `exit`: the exit status, or `null` when the program did not end.
|
|
43
|
+
- `out`: standard output.
|
|
44
|
+
- `problems`: what decided a reject or an unknown, each with its kind, node, the standard's clause (C11 for C programs,
|
|
45
|
+
C++17 for C++ ones; the C library is C11's in both) and reason.
|
|
46
|
+
- `assumes` (only when present): the implementation's choices the result depends on, `[{implementation, choice}]`.
|
|
47
|
+
The library makes them as libc++ does (`vector.growth`: capacity and when `push_back` reallocates; `library.what`:
|
|
48
|
+
the text of `what()`); a choice of another implementation names it (`gcc:union.typePunning`).
|
|
49
|
+
- A program on a board adds the pins, the environment and the clock (see `@cella-lang/arduino`).
|
|
50
|
+
|
|
51
|
+
## Type query
|
|
52
|
+
|
|
53
|
+
A branch's `types src candidates` answers what a block editor asks of a program that may have holes. A hole is
|
|
54
|
+
`{"k": "eHole", "n": "<node>#<slot>"}` (or `sHole` where the syntax needs a statement); a program with holes has the
|
|
55
|
+
verdict `unknown` with a `hole` problem. `candidates` is a JSON array of types written as C or C++ (`"int"`,
|
|
56
|
+
`"double"`, `"char *"`, `"std::string"`, `"struct S"`), the same way the result prints them.
|
|
57
|
+
|
|
58
|
+
```json
|
|
59
|
+
{"nodes": {"<node>": "int"},
|
|
60
|
+
"slots": {"<node>#<slot>": {"display": "expects int", "expects": "int",
|
|
61
|
+
"fits": {"double": {"level": "narrowing"}, "char *": {"level": "no", "reason": "…"}}}},
|
|
62
|
+
"errors": [{"at": "<node>", "reason": "…"}]}
|
|
63
|
+
```
|
|
64
|
+
|
|
65
|
+
- `nodes`: the type of each expression and declaration, before implicit conversions.
|
|
66
|
+
- `fits`: `exact` (no conversion), `convert` (an implicit conversion without loss), `narrowing` (with loss), `no`
|
|
67
|
+
(rejected, with the reason). The type checker decides: the hole stands for a value of the candidate type, and the
|
|
68
|
+
level comes from the conversions it puts around it, so overloads, `auto` and `std::cout << ?` follow the real rules.
|
|
69
|
+
- `expects`: the slot's target type when every type that fits is converted to the same one (`int x = ?`, a parameter,
|
|
70
|
+
`return ?`); `null` when the slot takes anything or depends on the candidate (`std::cout << ?`, `? + 1`, an overloaded
|
|
71
|
+
call). `display` is for developers.
|
|
72
|
+
- `errors`: statements that do not check. Checking goes on after them, so the other nodes still get their types.
|
|
73
|
+
|
|
74
|
+
## Modules
|
|
75
|
+
|
|
76
|
+
| Area | Modules |
|
|
77
|
+
|---|---|
|
|
78
|
+
| Syntax | `cfamily.syntax` (the surface syntax), `syntaxtypes`, `syntaxnodes`, `syntaxwalk`, `syntaxcollect` |
|
|
79
|
+
| Types | `integer` (the integer types), `representation`, `resolution` (written types to resolved ones), `layout`, `literals`, `rules` (where the dialects differ on the same construct), `typetext` (types written as C) |
|
|
80
|
+
| Checking | `typed` (the typed core syntax), `conversion`, `expressions`, `statements`, `lifting`, `statics`, `tables`, `program` |
|
|
81
|
+
| Running | `memory` (objects, pointers as paths, bytes as the target represents them), `arithmetic`, `behavior` (what the standard leaves open), `state`, `evaluation`, `execution`, `sequencing` (unsequenced accesses), `summaries` (what a function may read and write), `running` (a program to its verdict), `encoding` (text at the boundary) |
|
|
82
|
+
| C library | `clibrary`, `standardlibrary`, `librarycode` (the functions written in C), `formatting` (printf), `scanning` (scanf, strtod), `files` |
|
|
83
|
+
| Debugger | `debugging` (the machine for the debugger driver), `sessions`, `variables` |
|
|
84
|
+
| Editors | `querying` (the type query), `generate` (programs back to source) |
|
|
85
|
+
|
|
86
|
+
## Changes
|
|
87
|
+
|
|
88
|
+
See `CHANGES.md`.
|
|
Binary file
|
|
Binary file
|
package/cfamily.cell
ADDED
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|