I'm using Visual Studio 2010 as my IDE and for the most part it's totally cool with the cc65 specific source files. The only that that trips it up is the __fastcall__ convention with two trailing underscores. VS 2010 actually recognizes __fastcall as a keyword and colors it appropriately so long as it doesn't have the trailing spaces. Is __fastcall a standard convention that means the same thing as __fastcall__ in cc65? The reason I ask is that Intellisense for VS 2010 does a great job with my sources, but not so much with the header files in the cc65/include folder. The reason why is that it thinks that the __fastcall__ macro is an error and so each and every function defined in the include files parses as an error and there are literally over 100 intellisense errors reported on the header files. It's nothing *important* for this to work, but it would be nice if it did. If cc65 could accept __fastcall as the same thing as __fastcall__ then the header files could be updated to the __fastcall convention and intellisense would be happy which would make VS just that much more awesome for cc65 development (which it is already pretty awesome). -- Payton Byrd <http://www.paytonbyrd.com> <http://it.toolbox.com/blogs/paytonbyrd> ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Mon May 3 03:12:09 2010
This archive was generated by hypermail 2.1.8 : 2010-05-03 03:12:13 CEST