999.999 release note says:
Programming Language/Script Editor
• Improved PowerLanguage Editor functionality and reliability
• Considerable number of reserved words added
Would you update what reserved words are added?
HaeRim
InvestWare, Inc.
http://www.investware.net
Please update the newly added reserved words
- Marina Pashkova
- Posts: 2758
- Joined: 27 Jul 2007
How about I_OpenEquity, I_ClosedEquity?
Without these words, is there some different way to plot an equity curve?
And, why am I told that I have a successful compile when these words are in red and the result does not work?
------ Build started: ------
Study: "Strat Equity Color" (Indicator)
Please wait ....
21.09.07 00:37:09
------ Compiled successfully ------
Without these words, is there some different way to plot an equity curve?
And, why am I told that I have a successful compile when these words are in red and the result does not work?
------ Build started: ------
Study: "Strat Equity Color" (Indicator)
Please wait ....
21.09.07 00:37:09
------ Compiled successfully ------
I cannot start programming more or less complex things without knowing which words are supported. After the first error messages i don't even know how to do the workarounds as they also could not work.Hi Haerim,
At the moment, we are not planning to update the supported reserved words list. In the 2.1 release almost all of the words are supported.
Should you have problems with any please let us know.
Please update the list. Should be a matter of minutes for you.
Maybe it is easier for you to post the not supported words.
Regards
Robert
- Marina Pashkova
- Posts: 2758
- Joined: 27 Jul 2007
- Marina Pashkova
- Posts: 2758
- Joined: 27 Jul 2007
Please consider that when essential information is missing in "the field", the lack of that information has a peristent negative impact on every potential user of that information.
Failure to distribute information that is "available at home base" into the hands of users/developers/partners who need it is one of the most critical failures in business process that can be allowed to occur.
Coding, testing, etc. may be 99% of a software job, but until you finish the job by making the necessary info available to the users, you get not much more than 0% of the intended customer-enabling effect of all that work.
I tell you directly and honestly, you need to rethink the priority you are giving to making necessary information available. Only an emergency fix to an actually broken mission-critical portion of the code is a legitimately higher priority. ALL new development must take 2nd place to fully informing users about prior development, else you have got your priorities completely backwards from where they need to be for success.
Failure to distribute information that is "available at home base" into the hands of users/developers/partners who need it is one of the most critical failures in business process that can be allowed to occur.
Coding, testing, etc. may be 99% of a software job, but until you finish the job by making the necessary info available to the users, you get not much more than 0% of the intended customer-enabling effect of all that work.
I tell you directly and honestly, you need to rethink the priority you are giving to making necessary information available. Only an emergency fix to an actually broken mission-critical portion of the code is a legitimately higher priority. ALL new development must take 2nd place to fully informing users about prior development, else you have got your priorities completely backwards from where they need to be for success.
- Marina Pashkova
- Posts: 2758
- Joined: 27 Jul 2007