Hi Albert, > Also noted that the jal-parser.exe in > the bin directory is different from the one in the source directory, > maybe you should only use it once I fixed this for now. My intention is to keep the windows bin updated to the latest more or less working version. Sources will follow my actual development.
> It would be nice to have the AT function, if > available, the device file can be JAL only without the J2C statements It is on the top of my list. In case you're interested: multitest.jal (also) contains my to-do list. Besides some smaller tasks, bit-vars, at and arrays are on the top part. And of course testing, which requires the creation of JAL code that output numbers with 'print_var' in such a way that proper operation can be verified. I expect there will be some rework as a result of this. In JAL you can use a variable that exists in C, without the need to declare it. The default type is byte and you can declare an other type with: var dword TRISD is TRISD (with two times the same identifier). Note that JAL requires stronger enforcement of typing than currently implemented in JAT. But that is going to change ;) Joep -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
