Don’t Blame the User for Misusing Your API


A conversation the other day got me thinking about interfaces.  As the author of an interface, it is easy to blame the users for its misuse.  I think that’s the wrong place for the blame.  An interface that is used incorrectly is often poorly written.  A well-written one will be intuitive for most people.  On the other hand, a poorly-designed one will be difficult for many people to operate.  Sure, properly educated users could use even a poor interface and even the best interfaces can be misused by incompetent users, but on average a good interface should intuitively guide the users to make the right decisions.  I’ll focus mostly on programming interfaces but the same facts are true for user interfaces.


One of the rules in our coding standard is that memory should be released in the same scope in which it was allocated.  In other words, if you allocate the memory, you are responsible for making sure it is released.  This makes functions like this violations of our standard:



Object * GetObject(void)


{


    return new Object(parameters);


}


Why do we say this shouldn’t be done?  It is not a bug.  Not necessarily anyway.  If the person calling this function just understands the contract of the function, he’ll know that he needs to delete the Object when he’s done with it.  If there is a memory leak, it’s his fault.  He should have paid close attention.  That’s all true, but in practice it’s also really hard to get right.  Which functions return something I need to delete?  Which allocation method did they use?  Malloc?  New?  CoTaskMemAlloc?  It’s better to avoid the situation by forcing the allocation into the same scope.  This way there is much less room for error.  The right behavior is intuitively derived from the interface itself rather than from some documentation.  here’s a better version of the same function:



void GetObject(Object * obj)


{


    obj->Configure(parameters);


}


This second pattern forces the allocation onto the user.  Object could be on the stack or allocated via any method.  The caller will always know because he created the memory.  Not only that, but people are accustomed to freeing the memory they allocate.  The developer calling this function will know that he needs to free the memory because it is ingrained in his psyche to free it.


Here’s another example I like.   I’ve seen this cause bugs in production code.  CComPtr is a smart pointer to wrap COM objects.  It manages the lifetime of the object so you don’t have to.  In most cases if the CComPtr already points at an object and you ask it to assign something new to itself, it will release the initial pointer.  Examples are Attach and Operator=.  Both will release the underlying pointer before assigning a new one.  To do otherwise is to leak the initial object.  However, there is an inconsistency in the interface.  Operator& which retrieves the address of the internal pointer, p, does not release the underlying pointer.  Instead, it merely asserts in p!=NULL.  CComPtrBase::CoCreateInstance behaves similarly.  If p!=NULL, it asserts, but happily over-writes the pointer anyway.  Why?  The fact that there is an assert means the author knows it is wrong.  Why not release before over-writing?  I’m sure the author had a good reason but I can’t come up with it.  Asserting is fine, but in retail code it will just silently leak memory.  Oops.  Who is to blame when this happens?  I posit that it is the author of CComPtr.


When someone takes your carefully crafted interface and uses it wrong.  When they forget to free the memory from the first GetObject call above, the natural inclination as the developer is to dismiss the user as an idiot and forget about the problem.  If they’d just read the documentation, they would have known.  Sometimes it’s possible to get away with that.  If your interface is the only one which will accomplish something or if it is included in some larger whole which is very compelling, people will learn to cope.  However, if the interface had to stand alone, it would quickly be passed over in favor of something more intuitive.  Let’s face it, most people don’t read all the documentation.  Even when they do, it’s impossible to keep it all in their head. 


Very many times the author of the API has the power to wave a magic wand and just make whole classes of bugs disappear.  A better written API–and by that I mean more intuitive–makes it obvious what is and is not expected.  If it is obvious, people won’t forget.  As the author of an API, it is your responsibility to make your interface not only powerful but also intuitive.  Bugs encountered using your interface make it less appealing to use.  If you want the widest adoption, it is best to make the experience as pleasant as possible.  That means taking a little more time and making it not just powerful, but intuitive.


How does one do that?  It’s not easy.  Some simple things can go a long way though. 



  • Use explanatory names for classes, methods, and parameters. 

  • Follow the patterns in the language you are writing for.  Don’t do something in a novel way if there is already an accepted way of doing it. 

  • Finally, be consistent within your interface and your framework.  If your smart pointer class releases the pointer most of the time something new is assigned to it, that’s not enough.  It should be true every time.  To have an exception to the rule inevitably means people will forget the exceptional situation and get it wrong.

As I said at the beginning, this same rule applies to user interfaces.  If people have a hard time using it, blame the designer, not the user.  For those of you old enough to have used Word Perfect 5.x, recall the pain of using it.  There was no help on the screen.  Everything was done by function key.  F2 was search.  Shift-F6 was center, etc.   The interface was so unnatural that it shipped with a little overlay for your keyboard to help you remember.  Is it any wonder that the GUI like that in Microsoft Word, Mac Write, Final Copy (Amiga), etc. eventually became the dominant interface for word processing?  People could and did become very proficient with the Word Perfect interface, but it was a lot easier to make a mistake than it should have been.  The more intuitive GUI won out not because it was more powerful, but rather because it was easier.  Think of that when designing your next API or User Interface.  Accept the blame when it is used incorrectly and make it so the misuse won’t happen.  Keep it easy to use and you’ll keep it used.

Comments (4)

  1. Mark Sowul says:

    "Why not release before over-writing?  I’m sure the author had a good reason but I can’t come up with it."

    A million dollars says it’s because, to quote Raymond, "Back in the old days, programmers were trusted not to be stupid," and now we’re stuck because it’d break backwards compatibility.

    "…this same rule applies to user interfaces.  If people have a hard time using it, blame the designer, not the user."  Agreed, 100%.  But we went through that already.

  2. Maurits says:

    This doesn’t work so well for variable-size objects.  There are three distinct approaches for that:

    1) Have the callee allocate the memory and make the caller free it (IAudioClient::GetMixFormat)

    new/delete doesn’t work so well here, but CoTaskMemAlloc/CoTaskMemFree does.

    2) Have the caller allocate the memory blind, and return an error if there’s not enough space (sprintf_s); this requires several calls if the caller really wants something big to work.

    3) Return the needed buffer size if the caller passes NULL or a too-small buffer. (GetEnvironmentVariable).  This usually requires only two calls (although if the size of the desired object changes frequently, determinism vanishes.)

  3. Maurits says:

    > Why not release before over-writing?

    Because the user may be relying on the lack of a release.

    User A:

    CComPtr<IFoo> pFoo;

    GetFoo1(&pFoo); UseFoo1(pFoo);

    // BUG? better, pFoo = NULL;

    GetFoo2(&pFoo); UseFoo2(pFoo);

    User B:

    // BUG? better to put this inside the for loop

    CComPtr<IFoo> pFoo;

    list<IFoo*> lMyFoos;

    for (i = 0; i < n; i++) {

      GetFoo(i, &pFoo);

      lMyFoos.push_back(pFoo);

      // *if* pFoo is moved in here,

      // would need to pFoo->AddRef()

      // on the assignment

    }

    // later: use lMyFoos, and individually ->Release() them

    User C:

    // less defensible, perhaps

    void foo(CComPtr<IBar> *ppBar) {

      // do something with a pointer to a CComPtr

      // input/output parameter, perhaps?

    }

    CComPtr<IBar> pBar;

    foo(&pBar); // weird, but why not?

    Both users A and B are guilty of (minor?) bugs as commented.  User C is just high.

    Current API behavior causes User A to leak Foo1, but Users B and C work as designed.

    Let’s look at the alternative API behavior… call CComPtr<T>::m_p->Release() in CComPtr<T>::operator&()

    User A’s memory leak is fixed.

    User B now has a list of pointers to deleted memory.  If he’s lucky, he’ll access violate when he tries to use them.  It may be possible to convince User B that this is due to a bug in his code.

    User C has more justification for righteous anger when his foo() can’t access a meaningful IBar.  It may just be possible to convince C to use raw pointers rather than CComPtr… or it may not.

  4. Shane MacLaughlin says:

    "Is it any wonder that the GUI like that in Microsoft Word, Mac Write, Final Copy (Amiga), etc. eventually became the dominant interface for word processing?"

    Interesting analogy between user interfaces and APIs.  As Mark Sowul said, there is an onus on programmers not to break legacy code with API updates.  My take on this is that if we change an API, good practice is to leave the legacy interface in tact, and add a new expanded version of it.  e.g. In MFC you have …Ex versions of many functions such as GetWindowOrg, GetWindowOrgEx, which not only supports legacy code, but also legacy coders who may not be interested in the newer version.

    Now look at the user interfaces.  Anyone else out there have a minor heart attack moving from MSVC 6, to VStudio 2003?  No more class wizard, a totally new UI, and IMHO a retrograde step for many C++ coders at the time.  And what about Office for Vista; look Ma, no menus!  Come back Word Perfect, all is forgiven.  

    Pity MS don’t have the same respect for legacy user interfaces that any good API developer would have for their users.