SkWriter32: throw in the SkTDArray towel.

SkWriter32: throw in the SkTDArray towel.

I think it's looking more clear we don't have a clean way to use SkTDArray in
SkWriter32.  We can't give SkWriter32 meaningful control over SkTDArray's
reallocation without making moot SkTDArray's raison d'etre.

Let's just use an SkAutoTMalloc<uint8_t> instead.  It wants SkWriter32 to
control it.  Also, it's lower overhead: SkAutoTMalloc<uint8_t> is just a smart
poiter: no size or capacity stored.

BUG=skia:

Committed: http://code.google.com/p/skia/source/detail?r=13436

[mtklein_C, 2014-02-13 16:53:57]

After seeing http://crrev.com/161063022, I'm starting to think our quest to
unify this stuff is more trouble than it's worth.  Here's my counterproposal.

[reed2, 2014-02-13 16:57:32]

lgtm

[mtklein_C, 2014-02-13 17:11:40]

On 2014/02/13 16:57:32, reed2 wrote:
> lgtm

I just removed the newly dead API from SkTDArray.h.  Worth another quick look.

[reed2, 2014-02-13 17:52:44]

lgtm

[mtklein, 2014-02-13 17:59:09]

The CQ bit was checked by mtklein@google.com

[commit-bot: I haz the power, 2014-02-13 17:59:16]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-02-13 17:59:17]

No LGTM from a valid reviewer yet. Only full committers are accepted.
Even if an LGTM may have been provided, it was from a non-committer or
a lowly provisional committer, _not_ a full super star committer.
See http://www.chromium.org/getting-involved/become-a-committer
Note that this has nothing to do with OWNERS files.

[reed1, 2014-02-13 18:06:24]

lgtm

[reed1, 2014-02-13 18:06:30]

The CQ bit was checked by reed@google.com

[commit-bot: I haz the power, 2014-02-13 18:06:37]

CQ is trying da patch. Follow status at
https://skia-tree-status.appspot.com/cq/mtklein@chromium.org/163983002/40001

[commit-bot: I haz the power, 2014-02-13 18:35:59]

Change committed as 13436