Re: [cc65] Difference between __fastcall and __fastcall__ ?

On Mon, May 3, 2010 at 6:39 AM, Oliver Schmidt <ol.sc@web.de> wrote:

> Hi Payton,
>
> >  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.
>
> I'm not using VS 2010 yet so I can't (re-)produce the issue.
> Nevertheless I could imagine very well, that this helps:
>
> Basically you need a preprocessor macro like
> #define __fastcall__ __fastcall
> which is only visible to VS intellisense. One way would to protect
> that define by an #ifdef __MSC_VER.
>
> However there's a much simpler and cleaner way as VS allows to define
> preprocessor settings for intellisense.
>
> On VS 2005 it's Project -> Properties -> Configuration Properties ->
> NMake -> IntelliSense -> Preprocessor Definitions. There you just
> enter
> __fastcall__=__fastcall
>
> After that at least VS 2005 shows for every __fastcall__ a tooltip
> saying "#define __fastcall__ __fastcall".
>
> I guess you'll agree that this is somewhat more appropriate than
> modifying cc65 ;-)))
>

Oh, absolutely.  I'm glad there's a workaround.  I had a HD failure last
night and so I get to rebuild my workstation (I'll never buy another Western
Digital HD, I've had 7 failures in 3 years).   Thank GOD I keep the sources
on CodePlex. :)

>
>



-- 
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.