Change SkAutoTUnref usage

I believe this is what you had intended. Before the SkData was exiting the if block with 2 refs (ostream & stream). In the new version it exits with 3 refs (+data). Nothing bad happened in the prior version (since the SkData was preserved by the ostream's ref) but I think this is better.

[Humper, 2013-01-14 15:17:59]

On 2013/01/14 13:37:39, robertphillips wrote:

Yeah, this looks better.  I admit I'm still not 100% on how these classes work.

[bsalomon, 2013-01-14 15:28:41]

On 2013/01/14 15:17:59, Humper wrote:
> On 2013/01/14 13:37:39, robertphillips wrote:
> 
> Yeah, this looks better.  I admit I'm still not 100% on how these classes
work.

AutoTUnref's whole job is to unref in his destructor. He never takes a ref, he
assumes one from whoever constructs him. All the other complexity in the
implementation is just about being able to use it in place of a T*.

Typical usage on the stack:

SkAutoTUnref<Foo> foo(functionThatReturnsANewlyReffedFoo());

Or if the AutoTUnref is used as a class member a setter might look like:

Foo* BarClass::setFoo(Foo* foo) {
    fAutoFooUnrefMember.reset(SkSafeRef(foo));
    return foo;
}

[reed1, 2013-01-14 15:29:56]

or

SkAutoTUnref<Foo> foo(new Foo);
...

Now the allocated foo will get cleaned up when 'foo' goes out of scope.

[robertphillips, 2013-01-14 17:40:50]

committed as r7155