The Weird and The Wonderful

ClementsDan wrote:

The JVM will always attempt a garbage collection before throwing an OutOfMemoryError

PIEBALDconsult wrote:

The rule of three: "The first time you notice something that might repeat, don't generalize it. The second time the situation occurs, develop in a similar fashion -- possibly even copy/paste -- but don't generalize yet. On the third time, look to generalize the approach."

AEternal wrote:

sometimes this is done to make things clearer to other coders (especially less-experienced ones).

if (x == true)
  return true;
else
  return false;

//  the previous snippet could be replaced with
//  return x;
//  but i have chosen not to use this so that junior-programmers
//  can understand how two different values can be returned by one single function
//  
//  To other senior programmers. Please leave the previous snippet or replace it by
//  another snippet that would clarify the problem even better

return x ;

// If I ever catch any of you writing it as 
//
// if (x == true)  
//   return true;
// else  
//   return false;
//
// I'll have you tied to an anthill and covered in honey!

PIEBALDconsult wrote:

I'll have you tied to an anthill and covered in honey!

return (x == true) ? true : false;

codemunch wrote:

class Person
{
public string FirstName;
public string LastName;
}

class PersonFascade
{
public void InsertPerson(Person p) { /* do stuff */ }
public void UpdatePerson(Person p) { /* do stuff */ }
public void DeletePerson(Person p) { /* do stuff */ }
}

x => if (SomeBoolMeth(x) == true) return true; return false ;