C# anonymous methods also support lexical closures (unlike Java anonymous inner classes).

You could replicate anonymous methods and lexical closures with a lot of code in VB.NET (temporary classes, etc) but replicating complicated iterators would not require just code, but a lot of algorithm/state-machine design and thought for every individual iterator you write.

You can find examples of both features all over the web so I won’t bother posting examples here…

I’m a pretty big advocate of functional and declarative languages. I use both anonymous methods and iterators *extensively* in most of my C# projects.

I’ve come to the conclusion that money sucks, and the only solution is to stick my head in the sand and cry.

It is important to be consistent, and to understand which one you are using. I think the docs are a little light in VB wrt this.

If you think rounding is awful, try timezones.

i played with anonymous delegates at home the other day (see below). it’s just syntactical sugar but it is something you cannot do in vb. another more basic example would be literal strings.

these can be done in vb, just not as simply (imo etc etc)…

public IList GetUnansweredMessages()
{

return GetItems(“spc_incoming_message_get”
, delegate(SqlDataReader dr)
{
Model.IncomingMessage message = new Model.IncomingMessage();

message.Body = dr.GetString(“body”);

return message;

}
, new SqlParameter(“@message_filter”, 0));

}

delegate T PopulateDataReader(SqlDataReader reader);
IList GetItems(string procName, PopulateDataReader method, params object[] paramArray)
{
List list = new List();

using (SqlDataReader dr = ExecuteReader(procName, paramArray))
{
while (dr.Read())
{
list.Add(method(dr));
}
}

return list;
}