Hi Matt, I am not sure what to think of this. There is no requirement for print.jal to have such a function. It is just an assign and putting it in a function adds a large calling overhead is large. And calling takes more typing than the actual assignment. I do acknowledge debug.jal needs such a function, since it handle the conditional stuff. And please do add it. But I am not sure it is a good idea to add a similar funtion in print.jal. Yes, it looks similar. But we do need to recommend not to use it since it is a waste of resources. I'd like to hear how you and others on the list look at this.
Joep 2010/9/18 mattschinkel <[email protected]>: > I am now testing this debug lib within networking. One problem I see > is that the print lib does not have any print character procedure. In > order to make the two libs alike, I would like to add this procedure > to print: > > procedure print_char(volatile byte out device, byte in character) is > device = character > end procedure > > print_char (serial_hw_data, "A") > > -- > 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. > > -- 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.
