doylecnn / cqpsdk-rust Goto Github PK

Currently we declare const char* in C as *const u8 in Rust, however they are CString, who ends with a \0, and if you use CString or CStr to parse the bytes, they will ask for a *const i8 instead of *const u8.

// My current way translating *const i8 into primitive str.
let msgText = std::str::from_utf8(std::ffi::CStr::from_ptr(msg).to_bytes()).unwrap();

Although the primitive str's as_ptr returns a *const u8, and it is working in CQP and WinAPI, they are encoded in UTF-8, while CQP and WinAPI use cp936, which might lead to problems in the future.

So my idea is, replace all *const u8 with *const i8, and use encoding module to solve the encoding conflict.

If you have any idea about this, please don't hesitate to share.

I use Sublime Text to compose Rust code, and it's nice when working with UTF-8, however applications in Windows use non-Unicode encoding.

I am thinking about including an encoding module to translate UTF-8 to cp936 when calling APIs, and our code sticks with UTF-8, any ideas?