Invisible wrote:
> Darren New wrote:
> 
>> There are some who make good arguments against default parameters. 
>> Basically, if it's a default parameter, it should be a separate method 
>> call to set the value, because that's more OO.  E.g., if you have a 
>> default parameter for printing that says whether it should be 
>> landscape or portrait, that should be a value in the print-job 
>> instance, not a parameter specified on every call.
> 
> What *you* need is curried functions! ;-)
> 

Explain curried functions, please.

>> Sadly, C# syntax is starting to get really ugly. :-) I expect the 
>> overloading rules will soon almost be as bad as C++.
> 
> Well... it was based on C to start with, so it's never going to be 
> exactly "pretty", is it?

At least in C# you can't do function pointers.

-- 
~Mike

Post a reply to this message