Future C# features
-
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? Probably. I wouldn't find any use for them. Actually it would be quite distracting to see pictures where I expect code. "When a man sits with a pretty girl for an hour, it seems like a minute. But let him sit on a hot stove for a minute and it's longer than any hour. That's relativity." - Albert Einstein
-
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
Relax, I'm joking. Besides, since when did cheese become X rated? :)
-
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.
You have all that today, it's called C++. :-D :) (Not saying I disagree with any of those, although #3 would be the one I would least need to use.) "When a man sits with a pretty girl for an hour, it seems like a minute. But let him sit on a hot stove for a minute and it's longer than any hour. That's relativity." - Albert Einstein
-
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.
Errr, please see C++. :) Actually, I think Default Parameters would have been a nice feature. The alternative is to overload the method, but still... it just seems like extra work. Regards, Alvaro
If you want to get to the top, prepare to kiss a lot of bottom. -- despair.com
-
"Whibey" makes me cringe. Sounds like something i'd buy from Mr. Whipple. :suss:
Shog9
Let your mercy spill / On all these burning hearts in hell If it be your will / To make us well...
Shog9 wrote: Whibey sounds like some G-rated British insult: "That bloke's a real whibey." CheeseWeasle
-
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)
;I never read code. I just look at the pictures. cheers, Chris Maunder
-
// 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
using
statement at the top of your file...using foo = fooenum;
...and it will make
foo
be 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 Gandhijdunlap wrote: Well, you can alias things in a certain file True, but if you referr to little interface example you will see that my point was that typedefs are especially useful when used in global/cross-file scope. -Oz --- Grab WndTabs from http://www.wndtabs.com to make your VC6 experience that much more comfortable...
-
Relax, I'm joking. Besides, since when did cheese become X rated? :)
I was kinda talkin' bout Strippy...
Conclusion of the day, don't believe a developer, his mind is always changing. -Stephane Rodriguez.
-
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
igor1960 wrote: 1. Ability to compile mixed files written in any CLR languages in one assembly; This can already be done using the command-line compiler - just not VS.NET's built-in compiler -- Russell Morris "So, broccoli, mother says you're good for me... but I'm afraid I'm no good for you!" - Stewy
-
I was kinda talkin' bout Strippy...
Conclusion of the day, don't believe a developer, his mind is always changing. -Stephane Rodriguez.
:laugh: You have to admit though, she would be a nice addition to Whidbey. ;)
-
igor1960 wrote: 1. Ability to compile mixed files written in any CLR languages in one assembly; This can already be done using the command-line compiler - just not VS.NET's built-in compiler -- Russell Morris "So, broccoli, mother says you're good for me... but I'm afraid I'm no good for you!" - Stewy
This can already be done using the command-line compiler - just not VS.NET's built-in compiler Could they refference each other?... "...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
-
You have all that today, it's called C++. :-D :) (Not saying I disagree with any of those, although #3 would be the one I would least need to use.) "When a man sits with a pretty girl for an hour, it seems like a minute. But let him sit on a hot stove for a minute and it's longer than any hour. That's relativity." - Albert Einstein
Navin wrote: You have all that today, it's called C++. Really? Wow, I'll switch to C++ then. ;P Navin wrote: although #3 would be the one I would least need to use I don't use it much directly. However, I use some great libraries (Loki) that use MI "under the hood" a lot.
-
jdunlap wrote: Well, you can alias things in a certain file True, but if you referr to little interface example you will see that my point was that typedefs are especially useful when used in global/cross-file scope. -Oz --- Grab WndTabs from http://www.wndtabs.com to make your VC6 experience that much more comfortable...
-
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 like several of the features already suggested, but I will be really, really, really disappointed if the next version of C# doesn't have Edit-and-Continue, when we've already been informed that VB.NET will have it....:| John
"We want to be alone when we hear too many words and we feel alone when it has been a while since anyone has spoken to us." Paul David Tripp -- War of Words -
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
Others have mentioned the one thing I want. Default parameters!
-
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
Somehow providing delegate inheritance. Don't know how it could be done, but I'd like to be able to do something like the following...
class MadeHappyEventArgs : EventArgs {
...
}public delegate void MadeHappyEventHandler : EventHandler (Object sender, MadeHappyEventArgs e);
class MakeHappyControl : Control {
private static readonly Object MadeHappyEvent = new Object(); public event MadeHappyEventHandler MadeHappy { add { Events.AddHandler(MadeHappyEvent, value); } remove { Events.RemoveHandler(MadeHappyEvent, value); } } protected void OnMadeHappy() { RaiseEvent(MadeHappyEvent, new MadeHappyArgs()); } private void RaiseEvent(Object event, EventArgs args) { // The next line is what it would allow EventHandler handler = (EventHandler)Events\[event\]; if (handler != null) handler(this, args); }
}
Would be nice... It's a lot cleaner when you don't have to rewrite that
RaiseEvent
method for every type ofEventArgs
event. -
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 would just really like to see the Office Assitant integrated into the IDE. I just love that cute little clippy. Ok !really :rolleyes: X| [Edit] Someone beat me to it.. [/Edit] --Sig-- Adam Wimsatt www.liquidneon.com
-
This can already be done using the command-line compiler - just not VS.NET's built-in compiler Could they refference each other?... "...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
VS.NET uses the csc and vbc compilers...just not to their full extent.
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
-
igor1960 wrote: 1. Ability to compile mixed files written in any CLR languages in one assembly; This can already be done using the command-line compiler - just not VS.NET's built-in compiler -- Russell Morris "So, broccoli, mother says you're good for me... but I'm afraid I'm no good for you!" - Stewy
They are both the same compiler. I'm sure it's an IDE limitation. Chris Richardson