Seiki Batch Script > Structure

Errors

 

If you try typing in your own scripts you will probably meet our error reporting quite soon. For example

This gives you the line and character address of the last place where the script engine knew what it was doing and then what it thought it was doing. The line it was having trouble with is usually added to the message. In this case the problem was the missing quotation mark before the $n which stopped it being able to resolve $time( )+.

Remember that error character numbers do not refer to the exact error location but to the start of the thing that was not understood. If we knew that exactly what the error was we would fix it for you but we don’t.

One of the best errors is to spell variable names differently. Script is not up to realising that Hicell, Hicel and hicell are all supposed to be the same thing. As far as it is concerned if they are different then they are different. We try to trap for this by considering any variable that is read from but never set to be an error with a message like

Which indicates that a value called r was added/subtracted/anything to something but this cannot catch all possibilities.