So a file name "c:\hello.txt" will produce this error as part of the name \he.ĩ1 "You cannot nest jump commands within other jump commands." When specifying a file name for the Print() or FileAppend() words, files that start with any of the jump commands will produce this error. The end jump commands are:īefore these commands, a begin jump command must be used.
Tradestation easylanguage reference code#
This error is displayed when the code editor finds an end jump command without a begin jump command in a text string. Array names cannot start with a number nor any special character other than the underline (_).ħ9 "There are more than 65534 legs defined in the Search Strategy."Ĩ1 "An internal error occurred due to improper syntax."ĩ0 "The first jump command must be a begin: (\\hb,\\pb,\\wb)" The code editor displays this error whenever it finds an invalid name in an array declaration statement. The resulting number from multiplying the dimensions of the array can’t exceed 2 billion. This arrays will have rows 0 through 10 and columns 0 though 5 in other words, 11 rows and 6 columns. For example, an array declared using the following statement will have 66 elements: The number of elements is calculated by multiplying all the dimensions of the array. Input names cannot start with a number nor any special character other than the underline (_).ħ0 "Array size cannot exceed 2-billion elements."Īrrays can have up to 2 billion elements. The code editor will display this error whenever it finds an invalid name in a input declaration statement. Variable names cannot start with a number nor any special character other than the underline (_).įor example, this error will be generated when the following statement is verified: The code editor displays this error whenever it finds an invalid name in an variable declaration statement. The following statement will produce this error: The code editor displays this error whenever it finds a number that is outside the supported range (a number which is too big). An example of an invalid number is 100.b4. For example, if a letter is inserted by mistake in a number, the number will be high lighted and this error will be displayed. The code editor displays this message whenever it finds a typographical error in a number. For example, if it is not an EasyLanguage reserved word EasyLanguage function, or a declared user defined variable, array, or input name. This error is displayed whenever a word is not recognized by the code editor. IncludeSignal: "MyStrategy: 55 "This analysis technique cannot be applied because it references historical fundamental data."Ħ1 "Word not recognized by EasyLanguage." In the following example, an error is generated when attempting to include MyStrategy (that has not yet been saved) in the strategy being edited. This message appears when referencing a strategy that has been created but not verified or saved. Value1 = MyFunction 53 "The Strategy referenced has not been saved." In the following example, the assignment of the recently created MyFunction fails because the function itself has not yet been saved. The code editor displays this message when attempting to reference a function that has been created but not verified or saved. Value1 = AskSize 18 "The word "EXTERNAL" expected here."ġ9 "Property not recognized by EasyLanguage."Ĥ9 "Token version mismatch, do Verify All."ĥ2 "The function referenced has not been saved." For example, an attempt to access the AskSize of 3 bars ago generates an error. This error is displayed whenever a bars ago index is used with a server field reserved word since they do not contain historical data values. To see line numbers in the code editor, use the Tools > Option menu sequence and check the Line Numbers setting.īe aware that the error may not actually be at the location of the code marker but will often have occurred on a prior EasyLanguage word or line.ġ "Method arguments cannot be used as inputs due to their life time."Ĥ "Custom field name cannot be more than 20 characters." 17 "Historical data not available for server fields." Double clicking on an error line in the Output pane automatically moves the cursor in the code editor to the error location. The Output pane at the bottom of the TradeStation Station Development Environment is used to display multiple lines of errors, including a short description of the error, the document and line number of the EasyLanguage where the error was triggered, and the error number. The following is a list of error codes for possible syntax or compiler errors that may occur when you verify your EasyLanguage document.
Tradestation easylanguage reference verification#
TradeStation Development Environment EasyLanguage Verification (Syntax) Error Codes EasyLanguage Verification (Syntax) Errors
0 kommentar(er)
