http://www.hackification.com/2008/09/11/booleans-as-function-parameters-considered-harmful/ Fri, 23 Jul 2010 14:53:52 +0000 hourly 1 http://wordpress.org/?v=3.0.1 http://www.hackification.com/2008/09/11/booleans-as-function-parameters-considered-harmful/comment-page-1/#comment-32 Samuel Carlsson Sat, 30 Jan 2010 23:58:03 +0000 http://www.hackification.com/?p=43#comment-32 Enums are never the answer. In this situation I'd either go with a real class for Higlight or Visibility or both! That would make it obvious what the parameter was for. Also an object initializer would do the trick, i.e. "new Thing { Visible = false }". That comes with new drawbacks such as unability to specify required parameters and readonly fields. Perhaps named parameters comes to c# soon! Enums are never the answer. In this situation I’d either go with a real class for Higlight or Visibility or both! That would make it obvious what the parameter was for. Also an object initializer would do the trick, i.e. “new Thing { Visible = false }”. That comes with new drawbacks such as unability to specify required parameters and readonly fields. Perhaps named parameters comes to c# soon!

]]> http://www.hackification.com/2008/09/11/booleans-as-function-parameters-considered-harmful/comment-page-1/#comment-31 jarod Fri, 28 Nov 2008 19:33:26 +0000 http://www.hackification.com/?p=43#comment-31 If it's a Boolean state, provide a single method to test it with a name like isVisible() and then two other methods to turn it on/off, with names like beVisible() and beInvisible() If it’s a Boolean state, provide a single method to test it with a name like isVisible() and then two other methods to turn it on/off, with names like beVisible() and beInvisible()

]]>