.NET Languages Weblog - Recent Comments

aaaaa

Thu, 23 Oct 2008 12:11:29 GMT

aaa

aaaaa

Fixed

Fri, 20 Jun 2008 18:07:56 GMT

Jason Bock

Thanks for noticing.

Missing link?

Fri, 20 Jun 2008 16:13:02 GMT

Rik Hemsley

?

I'm Cool With var

Sun, 16 Mar 2008 15:55:33 GMT

Jason Bock

I didn't mean to say I didn't like var. It's more that I need to get in the mode of using it.

var

Sun, 16 Mar 2008 15:38:48 GMT

Rik Hemsley

What puts you off using 'var' in most places? I'm starting to get used to avoiding writing the name of the type I want when it's as obvious to any reader as it is to the compiler. I'm holding off doing this on 'work' projects until I'm sure there are no hidden problems, though.

Mr.

Sun, 17 Feb 2008 20:32:26 GMT

James Nathan

just wanted to know if you sent that to my email address

Mr

Sun, 17 Feb 2008 20:17:42 GMT

James Nathan

Very good information

C# needs macros

Sat, 09 Feb 2008 23:34:04 GMT

Andrew Norris

Yes -- while automatic properties are a step in the right direction in some cases, if you need anything out of the ordinary, they don't help. We have many classes that store their data in an internal DataRow, and automatic properties are useful in these situations as well.

While code snippets and related forms of code generation can help, they don't help if all the code using a given idiom needs to be refactored later. What would be nice is a macro system that allows you to specify a parameterized block of code -- in your example, it would be for a property that throws an ObjectDisposedException -- and then allows you to just reference the macro. If at some point in the future all the code that uses that macro needs to be updated, it's as easy as changing the macro.