You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
So far I can't think of a use for this library.
It is definitely not needed on forex, and there is no need for it on the stock exchange.
If you are talking about partial execution, it works in full swing on Forex. In particular, that is why asynchrony is very much in demand at Forex, and therefore this library can be useful.
Have you tested this library on the stock exchange?
I haven't tested it on the stock exchange, but the stock exchange and forex are technically the same for the library. You just get data about all transactions anywhere you want, whenever you want. That's all there is to it. So nothing depends on the type of market here.
In what case do you think it will be useful?
The library will come in handy when asynchrony comes in handy. This is any mass (more than one) sending of trade orders. There can be many scenarios:
It is necessary to experiment. I think that simultaneous writing/reading of a resource works the same way as with global variables, because writing in both cases is creation: ResourceCreate and GlobalVariableSet. The only difference between a resource and a global is that you cannot even theoretically write anything to a resource at the same time. With global variables it is possible.
In fact, reading a resource is getting a piece of data from memory. And if reading has started, writing a resource should not affect it, because writing is allocating another piece of memory. They can hardly overlap because the OS itself will most likely prevent them from doing so. That's why, from my point of view, there should be no load/save conflicts with resources. But of course it is better to ask the developers this question.
Isn't a resource with the same name the same resource (and a piece of memory, respectively)?
It's easy to check - you should write something long with a special mark at the end and read it in parallel. If not a whole message will be read, it means there may be a conflict.
Isn't a resource with the same name the same resource (and chunk of memory, respectively)?
Writing is creating another resource.
It is easy to check - you should write something long with a special mark at the end and read it in parallel. If not a whole message will be read, then there may be a conflict.
This test script shows that there is no conflict.
Recording is the creation of another resource.
This verification script shows that there are no conflicts.
I had something like that in mind:
It really doesn't seem to be lost.
I meant something like this:
It really doesn't seem to be lost.
This variant of the check does not take into account the change in the size of the resource and the data at the end of the resource.
This check variant does not take into account changes in the size of the resource and the data at its end.
Can previously written data remain in memory? How to clear it?
Can previously recorded data remain in memory?
Theoretically, this is possible. Therefore, you should check this as well.
How to clear it?
Forum on trading, automated trading systems and testing trading strategies
Libraries: TradeTransactions
fxsaber, 2018.09.20 16:23.
ResourceINT.Free(); // Deleted data from the resourceCleaning the resource - deletion.
Theoretically it can be allowed. That's why you should check it too.
There are no errors with two strings of different lengths:
No errors with two strings of different lengths either:
That's right. That's why I said that the original code checked it.
is accessing a class-wide attribute instead of an instance attribute.
The same goes for the class declarations, and you like to use macros so much that I never know whether your class declarations are macros or enums. Typically, by MQL standard conventions, you should only use ALLCAPS for enums, macros, and constants -- and CamelCase is used for class declarations. Also, variables are defined using snake_case, by MQL convention.
It is not my intention to offend you with my constructive-criticism, and I know you work very hard to make these libraries free for everyone, which is awesome and we need more devs like you. I know that I don't speak only for myself, and if you just made a minor tweaks to the style being applied then more developers would use your libraries. That is what you want, is it not?