I got the a "Cannot Sell from a SellShort strategy." error compiling the following code under MC 3.0 Beta:
-------------------------------------------------------------------
buy ("buy LE") next bar high stop;
sell short ("sell SE") next bar low stop;
buy to cover from entry ("sell SE") next bar low - 10 stop;
sell from entry ("buy LE") next bar high + 10 stop;
--------------------------------------------------------------------
Which is correct code that compiles in TS alright. The error occurs at the "Buy to cover" keyword. It seems like PL Editor mistaken "Buy to cover" with the "Sell" key word.
This problem didn't exist in the MC 2.1 version.
Please check. Thanks!
PL Editor compilation error
- Marina Pashkova
- Posts: 2758
- Joined: 27 Jul 2007
- Marina Pashkova
- Posts: 2758
- Joined: 27 Jul 2007
The new beta is amazing. EL speed is much better and data loading speed has improved. My hat is off to the programming team and I know they deserve a vacation.
However I've waited for a long time for this build (since Oct 07) and now that I have the build and I got this EL compilation error. The EL compiler is a fundamental piece, and without a working compiler there is not much I can do with the new MC build. This bug wasn't in the MC 2.1
Please make it a high priority fix...
However I've waited for a long time for this build (since Oct 07) and now that I have the build and I got this EL compilation error. The EL compiler is a fundamental piece, and without a working compiler there is not much I can do with the new MC build. This bug wasn't in the MC 2.1
Please make it a high priority fix...
- Andrew Kirillov
- Posts: 1589
- Joined: 28 Jul 2005
- Has thanked: 2 times
- Been thanked: 31 times
- Contact:
Glam_100,
Marina told you that it should be fixed by the end of February, because we are going to release Beta 2 with the rest of functionality and all known bug fixes. However we do understand that we need keep releasing hot fixes for Beta 1. This is why we decided to release the next hot fix this Tuesday. The bug you reported will be fixed in this build.
Marina told you that it should be fixed by the end of February, because we are going to release Beta 2 with the rest of functionality and all known bug fixes. However we do understand that we need keep releasing hot fixes for Beta 1. This is why we decided to release the next hot fix this Tuesday. The bug you reported will be fixed in this build.