> Now if only I could get the '__internal' to show up in blue in my source
> code, like other managed C++ keywords (like __sealed and __gc)...
This is not something that I have tried so take what follows with a grain of
salt.
This was possible with VC++ 6.0. When I searched the MSDN, I found
instructions for the old IDE and this link:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsintro7/html/v
xtskDefiningKeywordsInVisualC.asp?frame=true
which I think applies to VS.Net 2005.
I don't know if it works with the current version. Perhaps one of the MS
guys will set us straight.
Regards,
Will
ismailp - 08 Mar 2005 18:38 GMT
internal keyword works on whidbey. there is no leading __ stuff (i.e.
not __internal).
class A
{
internal:
void f(){}
}
when you write "public private" or "private public", compiler generates
a warning saying that "public private is deprecated, use internal".
intellisense on beta1 does not highlight internal keyword with blue
color like it does on public, private or other reserved words.
ismail
TT (Tom Tempelaere) - 09 Mar 2005 14:15 GMT
Hi,
All very interesting things. Thanks for the info.
Tom.
> internal keyword works on whidbey. there is no leading __ stuff (i.e.
> not __internal).
[quoted text clipped - 9 lines]
> intellisense on beta1 does not highlight internal keyword with blue
> color like it does on public, private or other reserved words.
TT (Tom Tempelaere) - 09 Mar 2005 14:17 GMT
Hey William,
It works!!! Cool, thanks :D
Tom T.
> > Now if only I could get the '__internal' to show up in blue in my source
> > code, like other managed C++ keywords (like __sealed and __gc)...
[quoted text clipped - 14 lines]
> Regards,
> Will