Structure rules. Learning how to structure programmes, exploring possibilities, errors, solutions, etc. - page 11
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
It's a crooked one, too. Using a switch... case and using a state machine pattern are two different things. You can tell from the text that there's no such thing as a pattern, just like in the article you cited.
It reads something like "I've invented a unique winning system..." and then a crooked martin statement.
O.K. What is the fundamental difference then?
There you go. That's what I needed to prove :)
Another way to do it. Using a switch... case and using a state machine pattern are two different things. You can see from the text that there's no trace of a pattern there as well as in the cited article.
But don't worry that the article about the state machine you've given says it in black and white:
Let's say now Vasya makes a project in C# and he needs a simple state machine for one type of objects. He writes something like this:
Then he goes on rambling about various frameworks and ready-made classes.
The conclusion of the article is as follows:
"And then Vasya got fed up and went back to the world's simplest finite state machine. He reworked it a bit and came up with the rules of how to write code in it."
First of all, I didn't cite any article. :)
Secondly, to take an article as the truth in the first instance just because someone cited it and it's on hubra is a bit... um...
A stone axe is also a kind of axe.
First of all, I didn't cite any article. :)
Secondly, to take an article as the truth in the first instance just because someone cited it and it's on hubra is a bit... um...
A stone axe is also a kind of axe.
Yes, I'm sorry, it was cited by Urain.
If this article describes a non-state pattern, then what is a true state pattern? If you can get the topo... code to the studio, let's discuss it.
An important exception: the logic of HFT algorithms is actually described by the execution method.
I almost agree.
On this basis, I plan to further intellectualise the trading driver, namely to equip it with "brains" for independent decision making in fast trend situations.
// (Which actually just shifts the trailing limit into a "negative area").
Well... I'll do some googling.
Here's an interesting idea.
I almost agree.
On this basis, I plan to further intellectualize the trading driver, namely to equip it with "brains" for making independent decisions in situations of a fast trend.
// (Which, in fact, simply moves the trailing limit into a "negative area").