Hi Joep,
Joep Suijs wrote:
I looked into the _irp error that Wayne reported.
I didn't follow that, sorry if I repeat what has already been discussed.
It is caused by the use of string array in the procedure print_string(). Arrays seems not to be supported on 12f509. Can anybody confirm this?
Indirect addressing is not supported by this chip, so if a library uses indirect addressing it should check if the chip supports it. In general: if a library uses a feature which is not present in every PIC it should generate an error message when used with a chip without that feature. When it is a safety measure (like disabling interrupts on a chip without interrupt system) it could proceed without warning. Both these types of conditional compilation seem appropriate to me.
And if so, how can we handle this? For this particular case we could add conditional compile (based on de definition of _irp ?) for this procedure, but should we do this for each library that uses an array?
Beware with this test: for example the 16F683 has a STATUS_IRP bit, but the datasheet tells us that this bit is reserved! Maybe a check on 'core' would do, but that may be too general.
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.
