DawnHustig.surname();

In the event that we get married in the future, Dawn and I have discussed what to do about surnames. Here's a solution that we came up which randomizes which surname to use:

char * DawnHustigSurname::getSurname(void)
{
  int coin_flip=rand()%2;
  int surnameSize=0;
  delete surname;
  if (coin_flip)
  {
    surnameSize=sizeof("Hustig");
    surname = new char[surnameSize+1];
    strncpy(surname,"Hustig",surnameSize);
    surname[surnameSize]="\0";
  }
  else
  {
    surnameSize=sizeof("Schultz");
    surname = new char[surnameSize+1];
    strncpy(surname,"Schultz",surnameSize);
    surname[surnameSize]="\0";
  }
  return surname;
}

Signature:
  DawnHustig.getSurname();

Silliness aside, the dilemma we face is that Hustig isn't a very common last name, so there's some desire on Dawn's part to retain it. No existing solutions that I've seen for retaining surnames seems to work once one takes into consideration what children will do when they marry. For example, it might put a child with surname Schultz-Hustig in a bind when they marry--which surname to retain? People seem to accept the existing system because it's good enough, even though it has flaws (in my opinion).