I'm not sure if it works, but I tried it myself, and when I ordered with exchange.IO, if I used _C, it would be out of date, I don't know why.
Can the administrator list both the supported and unsupported functions in _C?
Thank you.
The Little Dream_C is all error-prone functions, because the first parameter of _C is the function reference. However, it is possible that some functions are not recommended to be handled with _C, such as the sub-unit function. If the price precision, sub-unit precision, etc. in the sub-unit function do not meet the requirements of the exchange (this is just an example of one possible, and there are other possible problems), then there will be an infinite number of errors, infinite repetition, and the policy is stuck here.
The Little DreamThe debugger itself has a time-out mechanism, but the real disk doesn't, so it could cause a crash in a similar scenario.
bamsmenAfter a few tests, I guess in the debugging tool, using _C will be out of date, and the feeling is a reminder!