The Function Name Hall of Shame: Round Three

The previous lists can be found here and here.

  1. // Apparently we have given up on using enums or arrays
    // or other products of common sense (On a side note…sOriginPoint?!?)
    const string DecodeBoolean(const bool bBoolean)
    string sOriginPoint = (bBoolean) ? “TRUE” : “FALSE”;
    return sOriginPoint;
  2. // Whatever excuse is made to justify calling it, the answer is still “no”
    bool EnsureFunctionIsCalled()
    bool bSuccess = true;
    return bSuccess;
  3. // I’m lost now, and I need GPS
    void LoadPreLoadMapForPostUnloadProcessStep(…)
  4. // Well, yeah, it would only be one of them…but that still doesn’t explain what
    // a return value of ‘True’ means…

    const bool RealErrorOrNotError(string& sMessage)
  5. // Personally, I like my programming to be a little more decisive
    void SetIsHashableIsMayBeHashable(string& sIsHashable)

Peter Bolton is the author of Blowing the Bridge: A Software Story and has also been known to be a grumpy bastard on occasion.

2 thoughts on “The Function Name Hall of Shame: Round Three

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s