OK, I have found the problem may be on the "pointers to arrays" (that is, double pointers) that lie beneath to example code. I knew this was a strage way of using an array but I wanted to do it this way to be consistent with other modules where instead of an array of pointers to functions I have a *structure* of pointers to functions. Anyway, I have understood I can not abstract a pointer to an array (that is, a pointer to the pointer to the first element) because array address is not present in memory... I feel the error is in gcc side now, because it stops warning me about this misuse when I do it through a typedef. Will post in their list. I am sorry for the false report :-( Regards, -- Carlos Sánchez de La Lama <csanchez@sidsa.es> ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Tue Jun 7 15:51:09 2005
This archive was generated by hypermail 2.1.8 : 2005-06-07 15:51:11 CEST