vasile surducan wrote:
> I've also noticed the "port_x_low_direction" and "port_x_high_direction" > has been removed from the jallib configuration file: I have not noticed that these have disappeared. If so that is not on purpose and you may open a Jallib issue for that. But please mention the 'buggy' device file. > var byte strisa > strisa = all_input > > procedure _trisa_flush is > assembler > bank movfw strisa > tris 5 > end assembler > end procedure > > procedure port_a_low_direction'put( byte in d ) is > var volatile byte a at strisa = ( strisa & 0xF0 ) | ( d & 0x0F ) > _trisa_flush > end procedure > > There is a better replacement for this option, except direct tris > manipulation? Are you converting old Jal programs to JalV2 and Jallib? That would explain some of your problems. The Jallib device files use here and there a slightly different naming convention. For example: "port_x_high_direction" is called "portX_high_direction" See also jallib/doc/html directory 'devicefiles.html'. Regards, Rob. -- Rob Hamerling, Vianen, NL (http://www.robh.nl/) -- 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.
