On Sun, Aug 23, 2009 at 10:01:20AM +0200, Oliver Schmidt wrote: > No feedback at all on my posting above ? I'm sorry. I have been busy and it's difficult for me to comment on that without doing some lengthy checks. I have never seen a framework that loads main() from a library and I would need to check the standard to see if this is legal or triggers undefined behaviour. And to understand, why there is no other way, than to have main() in the library, I would have to study Contiki to some extent. All this takes time which I think is at the moment is better spent on cc65. > Just imagine forgetting or misspelling main(). Wouldn't you expect the > linker (called with -t <target>) to complain about not being able to > resolve the symbol '_main' ? It's not worse than what happened before the change. If someone forgot to link in the startup code (which in my eyes is a lot easier than having a typo in "main"), he got exactly the error messages you're complaining about. This is now fixed. Yes, you're right, there are still things that could be improved. It's all a question of importance. For now, I can live with the described behaviour, because I know it was worse before. Breaking Contiki is more important to me, but currently I cannot tell how to fix that problem most easily. But I will definitely not go and start making changes to the linker before the changes to the compiler have been debugged and are stable to some extent. Regards Uz -- Ullrich von Bassewitz uz@musoftware.de ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Sun Aug 23 23:08:23 2009
This archive was generated by hypermail 2.1.8 : 2009-08-23 23:08:25 CEST