title: Is this a valid reason for an empty try catch or is there a more elegant solution?
body: <p>Assume I have the following class hierarchy:  </p>
  
  <p>A Person object contains a Customer object and the Customer object contains an Address object.</p>
  
  <p>I do not care if the customer has an address or not, but if they do, I want to save it to the database.  So in this case, is it perfectly fine to have something like:</p>
  
  <pre><code>try
  {
       Address addr = person.Customer.Address;
       db.SaveAddress(addr);
  }
  catch
  {
      //I don't care, but if it is there, just save it.
  }
  </code></pre>
  
  <p>In the above, I don't care if Customer is null or Address is null.  The other alternative I had was</p>
  
  <pre><code> if(person.Customer != null)
   {
       if(person.Customer.Address != null)
       {
  
       }
   }
  </code></pre>
  
  <p>The above can long though if the hierarchy is long.  Is there a more elegant way to check if a chain of objects is null without having to check each one.</p>