Future C# features
-
I am contracting at MS right now, and have contacts with the W------ people. I don't know if I am aloud to mention codenames, despite the fact that Microsoft made the name public, everyone knows the name of the product, and we have an article on it. I mentioned the W------ code name before, which was already publicized in the Microsoft roadmap, but then I was reminded of my NDA agreement; so I deleted the article. What sort of future C# features would you like to see in VS 2004 (or 2005, etc as the case may be)? Can't mention ship dates-- so I am being general, it's a future version of VS, and VS (2003 is already taken). I know the C# developer guys and the feature set is still fluid--uh I mean MORE fluid than usual. If I specify the absolute level of fluidity, I might give away trade secrets. Give me some of your ideas and I will relay them to the C# developers. I am on a company mailing list in which they are asking for feedback, comments and wishlists. Thanks, Wes
-
I am contracting at MS right now, and have contacts with the W------ people. I don't know if I am aloud to mention codenames, despite the fact that Microsoft made the name public, everyone knows the name of the product, and we have an article on it. I mentioned the W------ code name before, which was already publicized in the Microsoft roadmap, but then I was reminded of my NDA agreement; so I deleted the article. What sort of future C# features would you like to see in VS 2004 (or 2005, etc as the case may be)? Can't mention ship dates-- so I am being general, it's a future version of VS, and VS (2003 is already taken). I know the C# developer guys and the feature set is still fluid--uh I mean MORE fluid than usual. If I specify the absolute level of fluidity, I might give away trade secrets. Give me some of your ideas and I will relay them to the C# developers. I am on a company mailing list in which they are asking for feedback, comments and wishlists. Thanks, Wes
Excuse me, when I said "I deleted the article," I meant "I deleted the message in the article," which contained nothing secret except the publicized code name of a future version of a software development product sold by a very large software company that allows one to program in one or more of the standard visual programming languages for a popular operating system. Thanks, Wes
-
I am contracting at MS right now, and have contacts with the W------ people. I don't know if I am aloud to mention codenames, despite the fact that Microsoft made the name public, everyone knows the name of the product, and we have an article on it. I mentioned the W------ code name before, which was already publicized in the Microsoft roadmap, but then I was reminded of my NDA agreement; so I deleted the article. What sort of future C# features would you like to see in VS 2004 (or 2005, etc as the case may be)? Can't mention ship dates-- so I am being general, it's a future version of VS, and VS (2003 is already taken). I know the C# developer guys and the feature set is still fluid--uh I mean MORE fluid than usual. If I specify the absolute level of fluidity, I might give away trade secrets. Give me some of your ideas and I will relay them to the C# developers. I am on a company mailing list in which they are asking for feedback, comments and wishlists. Thanks, Wes
I can't think of anything that I want in C# more than what's being proposed in version 2. If you could, however, track down the ASP.NET guys and shoot the person who developed VS.NET's "support" for CSS, I would be greatly indebted to you. :)
I have also lived some years in Spain, and there people don't accept that you speak bad spanish. I usually compensate by speaking loud and accusing people of being stupid because they don't understand me. It usually works quite well. -jhaga on non-native languages
-
I am contracting at MS right now, and have contacts with the W------ people. I don't know if I am aloud to mention codenames, despite the fact that Microsoft made the name public, everyone knows the name of the product, and we have an article on it. I mentioned the W------ code name before, which was already publicized in the Microsoft roadmap, but then I was reminded of my NDA agreement; so I deleted the article. What sort of future C# features would you like to see in VS 2004 (or 2005, etc as the case may be)? Can't mention ship dates-- so I am being general, it's a future version of VS, and VS (2003 is already taken). I know the C# developer guys and the feature set is still fluid--uh I mean MORE fluid than usual. If I specify the absolute level of fluidity, I might give away trade secrets. Give me some of your ideas and I will relay them to the C# developers. I am on a company mailing list in which they are asking for feedback, comments and wishlists. Thanks, Wes
1. Predictable destructors*. This is, along with templates (aka generics), the feature I miss most from C++. No, this doesn't need to be on the .NET infrastructure, I can show you some IL samples on how a compiler could acomplish this today. *When I'm talking about predictable destructors, people often start explaining GC to me. Hey, I know GC and what I need is much more simpler than C++ destructors. What I really need is a "special" method on a class that is called when some instance gets out of scope. It's similar to the semantics of the using (IDisposable x = ...), but what I want is an IDisposable that would be transparent to the caller. The compiler would then be able to take care of this, at least, if the consumer is C#. 2. Some smarter compiler warnings would be cool, too. More than warnings, I want a lint! Just like FxCop, but acting on source files, integrated on the IDE. What about alerting me I allocated a local IDisposable and did not called Dispose, right when I'm typing code? What about alerting me that a method is not called (unless you set some specific attribute)? 3. The code editor could be smarter, too. I know, people on the compiler team have nothing to do with it. But you know, I don't believe this: MS could exploit more the fact that a .cs file contains C# code, and make VS.NET editor being act more like a "code editor": a. It could feature some Martin Fowler refactoring, like "extract method from a series of statements", "extract interface", "extract superclass" and other niceties; b. Rescan code and automatically generating "using [namespace];" statements is easier, too, I've made a simple macro for this. c. Rename members: rename method, rename variable, rename field, etc. And automatically updating who's calling that member, but only who's calling that member. This would eliminate 50% the times I need to use find and replace. d. WTH I need to code using only text? MS Word is out there for more than 10 years and proved users love Rich Text Format. What about including pictures inside code? .cs files could still be "pure" text and include something like a HTML img tag, referencing something on the solution. Think how cool would be including a database diagram or a UML model as a comment. e. Please, on CodeDOM, give me a C# parser. This would allow me to construct very useful tools right into the IDE, without the need to resort to COCO/R. f. Visually setting properties on code and calling methods. When I right-click an object variable, I would like visually set some properties
-
I am contracting at MS right now, and have contacts with the W------ people. I don't know if I am aloud to mention codenames, despite the fact that Microsoft made the name public, everyone knows the name of the product, and we have an article on it. I mentioned the W------ code name before, which was already publicized in the Microsoft roadmap, but then I was reminded of my NDA agreement; so I deleted the article. What sort of future C# features would you like to see in VS 2004 (or 2005, etc as the case may be)? Can't mention ship dates-- so I am being general, it's a future version of VS, and VS (2003 is already taken). I know the C# developer guys and the feature set is still fluid--uh I mean MORE fluid than usual. If I specify the absolute level of fluidity, I might give away trade secrets. Give me some of your ideas and I will relay them to the C# developers. I am on a company mailing list in which they are asking for feedback, comments and wishlists. Thanks, Wes
Wesner Moise wrote: What sort of future C# features would you like to see in VS 2004 (or 2005, etc as the case may be)? 1. Make the GC optional and give us proper destructors. 2. const parameters and const methods. 3. Multiple inheritance. 4. Default parameters. 5. Non-member functions.
-
I am contracting at MS right now, and have contacts with the W------ people. I don't know if I am aloud to mention codenames, despite the fact that Microsoft made the name public, everyone knows the name of the product, and we have an article on it. I mentioned the W------ code name before, which was already publicized in the Microsoft roadmap, but then I was reminded of my NDA agreement; so I deleted the article. What sort of future C# features would you like to see in VS 2004 (or 2005, etc as the case may be)? Can't mention ship dates-- so I am being general, it's a future version of VS, and VS (2003 is already taken). I know the C# developer guys and the feature set is still fluid--uh I mean MORE fluid than usual. If I specify the absolute level of fluidity, I might give away trade secrets. Give me some of your ideas and I will relay them to the C# developers. I am on a company mailing list in which they are asking for feedback, comments and wishlists. Thanks, Wes
Doesn't your manager feel a little silly reminding you not to mention Whidbey when Whidbey is being bandied about everyone including, as you probably so politely pointed out, the VS.NET roadmap? Whidbey Whidbey Whidbey Whidbey... My absolute #1 priority for C# which I have told everyone and anyone in the frameworks and languages team that will listen is default parameters for methods. That's all I ask. cheers, Chris Maunder
-
1. Predictable destructors*. This is, along with templates (aka generics), the feature I miss most from C++. No, this doesn't need to be on the .NET infrastructure, I can show you some IL samples on how a compiler could acomplish this today. *When I'm talking about predictable destructors, people often start explaining GC to me. Hey, I know GC and what I need is much more simpler than C++ destructors. What I really need is a "special" method on a class that is called when some instance gets out of scope. It's similar to the semantics of the using (IDisposable x = ...), but what I want is an IDisposable that would be transparent to the caller. The compiler would then be able to take care of this, at least, if the consumer is C#. 2. Some smarter compiler warnings would be cool, too. More than warnings, I want a lint! Just like FxCop, but acting on source files, integrated on the IDE. What about alerting me I allocated a local IDisposable and did not called Dispose, right when I'm typing code? What about alerting me that a method is not called (unless you set some specific attribute)? 3. The code editor could be smarter, too. I know, people on the compiler team have nothing to do with it. But you know, I don't believe this: MS could exploit more the fact that a .cs file contains C# code, and make VS.NET editor being act more like a "code editor": a. It could feature some Martin Fowler refactoring, like "extract method from a series of statements", "extract interface", "extract superclass" and other niceties; b. Rescan code and automatically generating "using [namespace];" statements is easier, too, I've made a simple macro for this. c. Rename members: rename method, rename variable, rename field, etc. And automatically updating who's calling that member, but only who's calling that member. This would eliminate 50% the times I need to use find and replace. d. WTH I need to code using only text? MS Word is out there for more than 10 years and proved users love Rich Text Format. What about including pictures inside code? .cs files could still be "pure" text and include something like a HTML img tag, referencing something on the solution. Think how cool would be including a database diagram or a UML model as a comment. e. Please, on CodeDOM, give me a C# parser. This would allow me to construct very useful tools right into the IDE, without the need to resort to COCO/R. f. Visually setting properties on code and calling methods. When I right-click an object variable, I would like visually set some properties
Daniel Turini wrote: Please, on CodeDOM, give me a C# parser OK - I ammend my message below to add this too :) cheers, Chris Maunder
-
I am contracting at MS right now, and have contacts with the W------ people. I don't know if I am aloud to mention codenames, despite the fact that Microsoft made the name public, everyone knows the name of the product, and we have an article on it. I mentioned the W------ code name before, which was already publicized in the Microsoft roadmap, but then I was reminded of my NDA agreement; so I deleted the article. What sort of future C# features would you like to see in VS 2004 (or 2005, etc as the case may be)? Can't mention ship dates-- so I am being general, it's a future version of VS, and VS (2003 is already taken). I know the C# developer guys and the feature set is still fluid--uh I mean MORE fluid than usual. If I specify the absolute level of fluidity, I might give away trade secrets. Give me some of your ideas and I will relay them to the C# developers. I am on a company mailing list in which they are asking for feedback, comments and wishlists. Thanks, Wes
Wesner Moise wrote: Give me some of your ideas ... This is what I'm missing the most: 1. typedefs 2. statics, enum (and typedefs) in interfaces. The first exists in Java and I can't figure out why they didn't do in C#. This will be a big boost:
interface IFoo
{
// currently need to use abstract class to do this :(
public static final int ALL_FOOS_USE_THIS = 2;// currently need to use abstract class to do this :(
public enum foo_statuses { ... }// good 'ol C++ style type aliasing - not available at all
public typedef ISomeProxy::someEnum fooEnum;....
}3. Design by contract - Design by contract can help debug both at development and at runtime:
3.1 const objects/methods - one of the best compile-type aids as well as declarative help for the optimizer. 3.2 Complex contracts ala "D":
http://www.digitalmars.com/d/dbc.html[^] http://www.digitalmars.com/d/class.html[^] (search for the title "Invariants")
Class invariants are IMO a huge thing, helping enforce (and validate) the programmer's view of the world as well as helping to document the code.
-Oz --- Grab WndTabs from http://www.wndtabs.com to make your VC6 experience that much more comfortable...
-
1. Predictable destructors*. This is, along with templates (aka generics), the feature I miss most from C++. No, this doesn't need to be on the .NET infrastructure, I can show you some IL samples on how a compiler could acomplish this today. *When I'm talking about predictable destructors, people often start explaining GC to me. Hey, I know GC and what I need is much more simpler than C++ destructors. What I really need is a "special" method on a class that is called when some instance gets out of scope. It's similar to the semantics of the using (IDisposable x = ...), but what I want is an IDisposable that would be transparent to the caller. The compiler would then be able to take care of this, at least, if the consumer is C#. 2. Some smarter compiler warnings would be cool, too. More than warnings, I want a lint! Just like FxCop, but acting on source files, integrated on the IDE. What about alerting me I allocated a local IDisposable and did not called Dispose, right when I'm typing code? What about alerting me that a method is not called (unless you set some specific attribute)? 3. The code editor could be smarter, too. I know, people on the compiler team have nothing to do with it. But you know, I don't believe this: MS could exploit more the fact that a .cs file contains C# code, and make VS.NET editor being act more like a "code editor": a. It could feature some Martin Fowler refactoring, like "extract method from a series of statements", "extract interface", "extract superclass" and other niceties; b. Rescan code and automatically generating "using [namespace];" statements is easier, too, I've made a simple macro for this. c. Rename members: rename method, rename variable, rename field, etc. And automatically updating who's calling that member, but only who's calling that member. This would eliminate 50% the times I need to use find and replace. d. WTH I need to code using only text? MS Word is out there for more than 10 years and proved users love Rich Text Format. What about including pictures inside code? .cs files could still be "pure" text and include something like a HTML img tag, referencing something on the solution. Think how cool would be including a database diagram or a UML model as a comment. e. Please, on CodeDOM, give me a C# parser. This would allow me to construct very useful tools right into the IDE, without the need to resort to COCO/R. f. Visually setting properties on code and calling methods. When I right-click an object variable, I would like visually set some properties
Totally agree with you on everything but 3d, I don't really need UML models in my code or whatnot. DB diagrams might be nice. But what I'd really love is a CodeDOM parser. That would be awesome. leppie has pointed out to me that the Microsoft.VisualStudio.dll Assembly has a CodeDOM parser in it, but that it kinda sucks for handwritten code, and works marginally well with designer generated code...but that's kinda worthless now, isn't it...
I have also lived some years in Spain, and there people don't accept that you speak bad spanish. I usually compensate by speaking loud and accusing people of being stupid because they don't understand me. It usually works quite well. -jhaga on non-native languages
-
Totally agree with you on everything but 3d, I don't really need UML models in my code or whatnot. DB diagrams might be nice. But what I'd really love is a CodeDOM parser. That would be awesome. leppie has pointed out to me that the Microsoft.VisualStudio.dll Assembly has a CodeDOM parser in it, but that it kinda sucks for handwritten code, and works marginally well with designer generated code...but that's kinda worthless now, isn't it...
I have also lived some years in Spain, and there people don't accept that you speak bad spanish. I usually compensate by speaking loud and accusing people of being stupid because they don't understand me. It usually works quite well. -jhaga on non-native languages
David Stone wrote: Totally agree with you on everything but 3d, I don't really need UML models in my code or whatnot. DB diagrams might be nice. But what I'd really love is a CodeDOM parser. It was only a sample. Including pictures as comments would be very nice, like, uh, when you are designing some UI control and want to draw a schematic of the control and how the properties affect its size, and so on. Am I the only one to include pictures as part of my projects?
// Quantum sort algorithm implementation
while (!sorted)
; -
David Stone wrote: Totally agree with you on everything but 3d, I don't really need UML models in my code or whatnot. DB diagrams might be nice. But what I'd really love is a CodeDOM parser. It was only a sample. Including pictures as comments would be very nice, like, uh, when you are designing some UI control and want to draw a schematic of the control and how the properties affect its size, and so on. Am I the only one to include pictures as part of my projects?
// Quantum sort algorithm implementation
while (!sorted)
;Daniel Turini wrote: Am I the only one to include pictures as part of my projects? Yes. :-D
Flight to Redmond - £200 Bulldozer Rental - £100 Destroying the MS campus single handedly for not doing an Academic upgrade, PRICELESS! -Jonny Newman
-
I am contracting at MS right now, and have contacts with the W------ people. I don't know if I am aloud to mention codenames, despite the fact that Microsoft made the name public, everyone knows the name of the product, and we have an article on it. I mentioned the W------ code name before, which was already publicized in the Microsoft roadmap, but then I was reminded of my NDA agreement; so I deleted the article. What sort of future C# features would you like to see in VS 2004 (or 2005, etc as the case may be)? Can't mention ship dates-- so I am being general, it's a future version of VS, and VS (2003 is already taken). I know the C# developer guys and the feature set is still fluid--uh I mean MORE fluid than usual. If I specify the absolute level of fluidity, I might give away trade secrets. Give me some of your ideas and I will relay them to the C# developers. I am on a company mailing list in which they are asking for feedback, comments and wishlists. Thanks, Wes
1. Ability to compile mixed files written in any CLR languages in one assembly; 2. Reverse P/Invoke; 3. ability to overload QueryInterface (support for aggregation); 4. windowless Windows Form Control; 5. unions; =================================== Probably, that's already enough to make it C... hehehe "...Ability to type is not enough to become a Programmer. Unless you type in VB. But then again you have to type really fast..." Me
-
Doesn't your manager feel a little silly reminding you not to mention Whidbey when Whidbey is being bandied about everyone including, as you probably so politely pointed out, the VS.NET roadmap? Whidbey Whidbey Whidbey Whidbey... My absolute #1 priority for C# which I have told everyone and anyone in the frameworks and languages team that will listen is default parameters for methods. That's all I ask. cheers, Chris Maunder
Chris Maunder wrote: Whidbey Whidbey Whidbey Whidbey Chris, I think this is part of the marketing plan that is using the "bad secret dilema". The more often the secret is refered to the more press it gets at launch time. Regardz Colin J Davies
*** WARNING *
This could be addictive
**The minion's version of "Catch :bob: "It's a real shame that people as stupid as you can work out how to use a computer. said by Christian Graus in the Soapbox
-
I am contracting at MS right now, and have contacts with the W------ people. I don't know if I am aloud to mention codenames, despite the fact that Microsoft made the name public, everyone knows the name of the product, and we have an article on it. I mentioned the W------ code name before, which was already publicized in the Microsoft roadmap, but then I was reminded of my NDA agreement; so I deleted the article. What sort of future C# features would you like to see in VS 2004 (or 2005, etc as the case may be)? Can't mention ship dates-- so I am being general, it's a future version of VS, and VS (2003 is already taken). I know the C# developer guys and the feature set is still fluid--uh I mean MORE fluid than usual. If I specify the absolute level of fluidity, I might give away trade secrets. Give me some of your ideas and I will relay them to the C# developers. I am on a company mailing list in which they are asking for feedback, comments and wishlists. Thanks, Wes
1. The VS version of Clippy, "Strippy", who will be a bikini-clad C# female coder to help us feel ok to code w/o pants (or underwear?). 2. Give Strippy the ability to chew out Java coders with insults like, "Hey handsome, remember that real men only code C#, babay." 2. A supreme master namespace made entirely of gold. Call it "Midas-22". 3. A small WMP ActiveX control on the top toolbar that will give live video feeds from the real world where young programmers can dream of having the proverbial "life". 4. Support for a USB device that will allow allow Mountain Dew/Coffee/Guiness to be streamed into the mouths of coders in need. 5. Visual Studio should auto-detect coder mind-wandering. When VS detects such a situation, it will automatically insert Mountain Dew/Coffee/Guiness into the mouth of the coder through the said USB device. 6. Support for the cheese foundation for cheese-impaired children. 8. Generics, specifically, generic women in the form of blow up dolls. 9. I skipped 7 because it is the perfect number of Javeh thy God.
-
I am contracting at MS right now, and have contacts with the W------ people. I don't know if I am aloud to mention codenames, despite the fact that Microsoft made the name public, everyone knows the name of the product, and we have an article on it. I mentioned the W------ code name before, which was already publicized in the Microsoft roadmap, but then I was reminded of my NDA agreement; so I deleted the article. What sort of future C# features would you like to see in VS 2004 (or 2005, etc as the case may be)? Can't mention ship dates-- so I am being general, it's a future version of VS, and VS (2003 is already taken). I know the C# developer guys and the feature set is still fluid--uh I mean MORE fluid than usual. If I specify the absolute level of fluidity, I might give away trade secrets. Give me some of your ideas and I will relay them to the C# developers. I am on a company mailing list in which they are asking for feedback, comments and wishlists. Thanks, Wes
-
I am contracting at MS right now, and have contacts with the W------ people. I don't know if I am aloud to mention codenames, despite the fact that Microsoft made the name public, everyone knows the name of the product, and we have an article on it. I mentioned the W------ code name before, which was already publicized in the Microsoft roadmap, but then I was reminded of my NDA agreement; so I deleted the article. What sort of future C# features would you like to see in VS 2004 (or 2005, etc as the case may be)? Can't mention ship dates-- so I am being general, it's a future version of VS, and VS (2003 is already taken). I know the C# developer guys and the feature set is still fluid--uh I mean MORE fluid than usual. If I specify the absolute level of fluidity, I might give away trade secrets. Give me some of your ideas and I will relay them to the C# developers. I am on a company mailing list in which they are asking for feedback, comments and wishlists. Thanks, Wes
-
1. The VS version of Clippy, "Strippy", who will be a bikini-clad C# female coder to help us feel ok to code w/o pants (or underwear?). 2. Give Strippy the ability to chew out Java coders with insults like, "Hey handsome, remember that real men only code C#, babay." 2. A supreme master namespace made entirely of gold. Call it "Midas-22". 3. A small WMP ActiveX control on the top toolbar that will give live video feeds from the real world where young programmers can dream of having the proverbial "life". 4. Support for a USB device that will allow allow Mountain Dew/Coffee/Guiness to be streamed into the mouths of coders in need. 5. Visual Studio should auto-detect coder mind-wandering. When VS detects such a situation, it will automatically insert Mountain Dew/Coffee/Guiness into the mouth of the coder through the said USB device. 6. Support for the cheese foundation for cheese-impaired children. 8. Generics, specifically, generic women in the form of blow up dolls. 9. I skipped 7 because it is the perfect number of Javeh thy God.
Did you forget the PG rating on the Lounge? :suss:
youd ebtter bnot be taki8ng agvantage o f my mental abilites!1 -David Wulff one night over MSN while totally plastered
-
I am contracting at MS right now, and have contacts with the W------ people. I don't know if I am aloud to mention codenames, despite the fact that Microsoft made the name public, everyone knows the name of the product, and we have an article on it. I mentioned the W------ code name before, which was already publicized in the Microsoft roadmap, but then I was reminded of my NDA agreement; so I deleted the article. What sort of future C# features would you like to see in VS 2004 (or 2005, etc as the case may be)? Can't mention ship dates-- so I am being general, it's a future version of VS, and VS (2003 is already taken). I know the C# developer guys and the feature set is still fluid--uh I mean MORE fluid than usual. If I specify the absolute level of fluidity, I might give away trade secrets. Give me some of your ideas and I will relay them to the C# developers. I am on a company mailing list in which they are asking for feedback, comments and wishlists. Thanks, Wes
Not really C# but anyway. better interop tools : - better and more comprehensive tlbimp.exe (only a fraction of IDL modules are imported) - better and more comprehensive tlbexp.exe - axexp.exe better interop marshaling : - more seamless. Pre-interoperating the underlying WIN32 API would be the least to expect. features for the IDE : - intellisense on attributes - xml-driven attributes : when an attribute is expecting a filepath, the UI should have an open/file dialog fired up without being seen.
-
**MULTIPLE INHERITANCE!!!** With block **Optional/default parameters** Predictable destructors
"Blessed are the peacemakers, for they shall be called sons of God." - Jesus
"You must be the change you wish to see in the world." - Mahatma Gandhi -
Wesner Moise wrote: Give me some of your ideas ... This is what I'm missing the most: 1. typedefs 2. statics, enum (and typedefs) in interfaces. The first exists in Java and I can't figure out why they didn't do in C#. This will be a big boost:
interface IFoo
{
// currently need to use abstract class to do this :(
public static final int ALL_FOOS_USE_THIS = 2;// currently need to use abstract class to do this :(
public enum foo_statuses { ... }// good 'ol C++ style type aliasing - not available at all
public typedef ISomeProxy::someEnum fooEnum;....
}3. Design by contract - Design by contract can help debug both at development and at runtime:
3.1 const objects/methods - one of the best compile-type aids as well as declarative help for the optimizer. 3.2 Complex contracts ala "D":
http://www.digitalmars.com/d/dbc.html[^] http://www.digitalmars.com/d/class.html[^] (search for the title "Invariants")
Class invariants are IMO a huge thing, helping enforce (and validate) the programmer's view of the world as well as helping to document the code.
-Oz --- Grab WndTabs from http://www.wndtabs.com to make your VC6 experience that much more comfortable...
// good 'ol C++ style type aliasing - not available at all
public typedef ISomeProxy::someEnum fooEnum;Well, you can alias things in a certain file, but you can't alias them once and be done with it. You can put a
usingstatement at the top of your file...using foo = fooenum;
...and it will make
foobe able to be used as if it wasfooenum."Blessed are the peacemakers, for they shall be called sons of God." - Jesus
"You must be the change you wish to see in the world." - Mahatma Gandhi