Add more SK_API declarations to fix Chrome.

Add more SK_API declarations to fix Chrome.

TBR=ctguil@chromium.org

[reed1, 2011-05-31 12:08:30]

Can we not just put SK_API on the class definition line, instead of on each
method?

[Steve VanDeBogart, 2011-05-31 15:26:45]

There's a problem adding it to the class if there are templatized fields, or
something like that.  Chris knows the details.

--
Steve

On Tue, May 31, 2011 at 5:08 AM, <reed@google.com> wrote:

> Can we not just put SK_API on the class definition line, instead of on
> each method?
>
>
> http://codereview.appspot.com/4526088/
>

[reed1, 2011-05-31 15:40:03]

Templates are just awesome!

On Tue, May 31, 2011 at 11:26 AM, Steve VanDeBogart
<vandebo@chromium.org> wrote:
> There's a problem adding it to the class if there are templatized fields, or
> something like that.  Chris knows the details.
> --
> Steve
>
> On Tue, May 31, 2011 at 5:08 AM, <reed@google.com> wrote:
>>
>> Can we not just put SK_API on the class definition line, instead of on
>> each method?
>>
>> http://codereview.appspot.com/4526088/
>
>

[Chris Guillory, 2011-05-31 17:19:51]

LGTM.

If we put SK_API on the class we would need to export all of its members. For
the template members that includes specifically exporting the definitions for
the template instantiations that are used. It is possible to do that.