@@ -17,24 +17,25 @@ mod tests;
17
17
#[ cfg( feature = "debug" ) ]
18
18
mod log;
19
19
20
- use crate :: error:: OracleError ;
21
- use processor:: process_instruction;
22
-
23
- use solana_program:: entrypoint;
24
-
25
- //Below is a high lever description of the rust/c setup.
26
-
27
- //As we migrate from C to Rust, our Rust code needs to be able to interact with C
28
- //build-bpf.sh is set up to compile the C code into a two archive files
29
- //contained in `./program/c/target/`
30
- // - `libcpyth-bpf.a` contains the bpf version for production code
31
- // - `libcpyth-native.a` contains the systems architecture version for tests
32
-
33
- //We also generate bindings for the types and constants in oracle.h (as well as other things
34
- //included in bindings.h), these bindings can be accessed through c_oracle_header.rs
35
- //Bindings allow us to access type definitions, function definitions and constants. In order to
36
- //add traits to the bindings, we use the parser in build.rs. The traits must be defined/included
37
- //at the the top of c_oracle_headers.rs. One of the most important traits we deal are the Borsh
38
- //serialization traits.
20
+ use {
21
+ crate :: error:: OracleError ,
22
+ processor:: process_instruction,
23
+ solana_program:: entrypoint,
24
+ } ;
25
+
26
+ // Below is a high lever description of the rust/c setup.
27
+
28
+ // As we migrate from C to Rust, our Rust code needs to be able to interact with C
29
+ // build-bpf.sh is set up to compile the C code into a two archive files
30
+ // contained in `./program/c/target/`
31
+ // - `libcpyth-bpf.a` contains the bpf version for production code
32
+ // - `libcpyth-native.a` contains the systems architecture version for tests
33
+
34
+ // We also generate bindings for the types and constants in oracle.h (as well as other things
35
+ // included in bindings.h), these bindings can be accessed through c_oracle_header.rs
36
+ // Bindings allow us to access type definitions, function definitions and constants. In order to
37
+ // add traits to the bindings, we use the parser in build.rs. The traits must be defined/included
38
+ // at the the top of c_oracle_headers.rs. One of the most important traits we deal are the Borsh
39
+ // serialization traits.
39
40
40
41
entrypoint ! ( process_instruction) ;
0 commit comments