fedail said:
but the pin 15 is not work if don't programe it
i have program pins and the apl language use & for and
if you use this program and test it befor i will test ur example
Most Jedec compatible compilers will support at the least the following command operators:-
/ - invert - Precedence (4 Highest)
! - invert - Precedence (4)
* - Logical AND - Precedence (3)
& - Logical AND - Precedence (3)
| - Logical OR - Precedence (2)
+ - Logical OR - Precedence (2)
^ - Logical XOR - Precedence (1)
$ - Logical XOR - Precedence (1)
:+: - Logical XOR - Precedence (1)
= - Assignment - Precedence (0)
:= - Registered Assignment - Precedence (0 Lowest)
comments can use either a semicolon ( ; ) or curly brackets {}
e.g
;this is a comment
{both of these lines
are comments}
At the very least you should have a :-
Header
A Declaration Block
An Equation Block
Anything before the Declaration Block will be treated as a file header, this will be passed as the header for each generated file.
The Declaration Block is where your Device Identifier Keyword, usually just "CHIP", Pin List, and any compiler directives go. It's always a good idea to pre-define the complete pin list, you can edit whatever you need to change later. Anything before your Keyword will be treated as the file header.
Anything before your Equation Block will be treated as the Declaration Block.
After the Equation Block Identifier Keyword, usually just "EQUATIONS", the compiler will expect your equations using the various operators etc.
Some compilers like to have an "END" keyword after your equations to signify the end of the equations, others just read till they find an eof and treat that as the end of equations.
I suggest that you read up a little on the use of your compiler, the various meanings and significance of the operators, the compiler directives and syntax supported, and obviously the datasheet for the device you are using. The outline above may be different to the way your compiler expects things.
Hope this helps you
rgds