[seasoup]

Named parameters are awesome. The equivalent pattern in javascript is passing in an options object.

foo({ 'name': 'bar', 'title': 'Bar' });

This means not having to look up what the exact order of options are, nor having to pass in a bunch of null parameters because the one you want is the last parameter. Very cool.

}

[bruceboughton]

Named parameters will be particular useful when calling methods which take bools (rather than a intention revealing enum).

[rhythmAddict]

I agree that it makes it "more readable", but that only would matter if intellisense wasn't working. I see the parameters, and they are strongly typed. In JS, this isn't the case, so it is much more helpful (e.g, I can completley screw up types/params and they will probably materialize as some strange behavior. As far as bools, I generally try to avoid having more one or two bools as an argument, unless it's required, and it rarely is.

Obviously, all IMO.

[InclinedPlane]

Do you have intellisense in your eyes? A line of code with a handful of named parameters reveals its intentions (and possibly also its correctness) for more readily than a line of code with a laundry list of parameters that you need to mouseover then do a bit of mental juggling to line up which value lines up with which parameter. In doing so you've likely interrupted and degraded your reading of the code and you've definitely degraded your ability to readily spot the difference between correct and incorrect code.

[rhythmAddict]

Actually, you guys are right. I realized the flaw in my thought process right after I read seasoup's post.

I do, however, have intellisense in my eyes.

[TeHCrAzY]

Bingo. You can also avoid the fun Enum.IsDefined that comes with it.