Skip part of script

[alexstox]

Hello dear NT support and everybody! So, what if there is some part of script that I want to be skipped if some conditions come true?

Example:
if (A=3) do smth
else continue to read script

[NinjaTrader_Jesse]

Hello alexstox,

You can certainly use an IF statement to accomplish what you are trying to do. In fact the statement you posted would work as a simple switch to turn on and off sections of code using a variable.

Here is what your statement would look like in NinjaScript

private int A = 3;

protected override void OnBarUpdate()
{
if(A == 3)
{
// A is equal to 3 so this section of the if statement would be executed
}
else
{
// If A is not equal to 3 this part would be used instead. 
}
}

For this example the portion of code you would like to skip if A is equal to 3 would be the second half of the if Statement.

When using an IF statement it is always good to keep in the back of your mind, the only items that will belong in the if statement would be the items that need to be turned on or off using the variable. The rest of your code can remain outside of the IF statement so that it is properly executed.

I would like to provide this link to an MSDN article on IF statement usages. This is an excellent resource to take a look at as there are quite a few good examples.

http://msdn.microsoft.com/en-us/library/5011f09h.aspx

One note on this, Because NinjaScript is essentially C# programming language any C# tutorials you may find online can be helpful when writing NinjaScript.

Please let me know if I may be of additional assistance.

[ninZa]

Hello dear NT support and everybody! So, what if there is some part of script that I want to be skipped if some conditions come true?

Example:
if (A=3) do smth
else continue to read script

Hi alexstox,

I don't actually understand your question. Could you tell more clearly about what to be skipped? I edit your example a little bit to make it more general and easier for you to express your thought:

if (condition) Do_something_1;
else Do_something_2;

So, what do you want to be skipped? Do_something_1 or Do_something_2?

Thank you.
Pi

[alexstox]

What if script contains lots of conditions in different places of script. And I need to jump from one condition to another?
I just need to reverse position. But to do so, I need yo put some rules before long or short entries. That's why I thought to do it like this - check if smth happen before long entries, if yes - jump to short entries rules and do short...

Maybe you have some examples of reverse position in strategy with lots of rows =)))

[ninZa]

What if script contains lots of conditions in different places of script. And I need to jump from one condition to another?
I just need to reverse position. But to do so, I need yo put some rules before long or short entries. That's why I thought to do it like this - check if smth happen before long entries, if yes - jump to short entries rules and do short...

Maybe you have some examples of reverse position in strategy with lots of rows =)))

If I understand your question correctly, then this may be a solution. You can use the goto function to "jump / fly" to a label of your choice, anywhere in your code.

Example:

if (your_condition) goto Your_Label;

........ script to be skipped
........ script to be skipped
........ script to be skipped

Your_Label:
Do_your_work_here;

Learn more about goto statement: http://msdn.microsoft.com/en-us/libr...v=vs.100).aspx

[alexstox]

If I understand your question correctly, then this may be a solution. You can use the goto function to "jump / fly" to a label of your choice, anywhere in your code.

Example:


Learn more about goto statement: http://msdn.microsoft.com/en-us/libr...v=vs.100).aspx

Wow! It's cool! Thank you

[ninZa]

Wow! It's cool! Thank you

Glad to help you. Cheers

[koganam]

Wow! It's cool! Thank you

Be very careful, please. There is good reason why the goto statement is frowned upon by development teams. Such unconditional transfer of control makes code VERY hard to read much later, especially with code that has many complex branches. It is very easy to read when writing it: it is very hard to follow when being reviewed, whether by another person in QA, or the original author much later when the ideas are no longer fresh in the mind.

Every control structure can be implemented using "goto" statements, but this is best left to the compiler, not the high-level programmer. "goto" isn't considered harmful because of its positive effects but because of its negative consequences, and these negativities have been eliminated by structured programming, and its derivatives.

In the same vein, saying “GOTO is a tool, and as with all tools, it can be used and abused” is completely off the mark. As a parallel example, no modern construction worker would use a rock and claim it “is a tool.” Rocks have been replaced by hammers. Similarly, in high-level programming, "goto" has been replaced by control structures.

Now, of course, if the construction worker were stranded in the wild without a hammer, sensibly, he would use a rock instead. If a programmer has to use an inferior programming language that doesn't have modern, sensible, control structures, well, of course, one may have to use "goto" instead. But if one uses the goto statement anywhere else, instead of using the appropriate language feature, then clearly the language has not been properly understood, and the "goto" statement is still being wrongly used. It really is as "cut and dried" as that.

I am off the soapbox.

[alexstox]

Be very careful, please. ...

I am off the soapbox.

Thank you Big Brother