It's somewhat unclear what you are after. Why do you want to swap the pointer held by temp with the return value of a function, if you could just use assignment to the same effect?

But the technical reason is that swap takes the argument by non-const reference (as it is going to modify it), and temporaries (such as return values of function calls) cannot be bound to non-const references.

However, you can call methods on temporaries returned from functions, so the following should work:

GetCCDcallback(*otherptr, lastx, lasty, newx, newy).swap(temp);

As I understand it, reset() is there to allow you to give another naked pointer to the class. When you have a smart pointer, I don't see why you should avoid assignment, as it works correctly and is the default way of assigning something to something.

The .swap() member function accepts a non-const reference to another instance (which makes sense; after all, the purpose is to modify the other instance, by causing it to "become" the current one, and vice-versa). You can't pass a temporary by non-const reference. It's a language feature intended to prevent certain kinds of errors. (Basically: the purpose of passing by non-const reference is to make changes to the caller's data, which the caller can then "see". But since a temporary is, well, temporary, there is no way to examine the changes to it. The conclusion is that you might be doing something wrong if you explicitly ask for changes that you can't examine.)

It appears that what you really want to do is set 'temp' to whatever is returned from the callback function (since you are swapping with 'temp2' and then apparently don't care about that variable). To do this, you can just assign (i.e., use the operator=, which has been carefully overloaded for boost::shared_ptr).