Add FileIOTrusted class.

Add FileIOTrusted class.
BUG=none
TEST=none

[sehr (please use chromium), 2011-12-08 18:05:59]

I think it would be good to have a wrapper class for this interface.  Please let
me know what you think.

[brettw, 2011-12-08 18:29:33]

How much easier does this make your life? I've been advocating no (or fewer) C++
wrappers for trusted interfaces. The C++ wrapper goes to everybody and get
linked with nacl plugins, so I'm worried that they may be confusing or cause
bloat. And things like this class are only usually used by one caller and in one
place.

If you have different code that uses it and it makes your life easier, we should
maybe add it. Or you can just put the wrapper in your code. Let me know what you
think, there's not really a hard rule...

[sehr (please use chromium), 2011-12-14 19:33:56]

OK, if that's the philosophy, I'll drop the CL.  I just found the mixture of C
and C++ interfaces in the same client a bit jarring.

On 2011/12/08 18:29:33, brettw wrote:
> How much easier does this make your life? I've been advocating no (or fewer)
C++
> wrappers for trusted interfaces. The C++ wrapper goes to everybody and get
> linked with nacl plugins, so I'm worried that they may be confusing or cause
> bloat. And things like this class are only usually used by one caller and in
one
> place.
> 
> If you have different code that uses it and it makes your life easier, we
should
> maybe add it. Or you can just put the wrapper in your code. Let me know what
you
> think, there's not really a hard rule...

[sehr (please use chromium), 2011-12-15 21:40:23]

Reopened at Brett's suggestion.

On 2011/12/14 19:33:56, sehr wrote:
> OK, if that's the philosophy, I'll drop the CL.  I just found the mixture of C
> and C++ interfaces in the same client a bit jarring.
> 
> On 2011/12/08 18:29:33, brettw wrote:
> > How much easier does this make your life? I've been advocating no (or fewer)
> C++
> > wrappers for trusted interfaces. The C++ wrapper goes to everybody and get
> > linked with nacl plugins, so I'm worried that they may be confusing or cause
> > bloat. And things like this class are only usually used by one caller and in
> one
> > place.
> > 
> > If you have different code that uses it and it makes your life easier, we
> should
> > maybe add it. Or you can just put the wrapper in your code. Let me know what
> you
> > think, there's not really a hard rule...

[brettw, 2011-12-15 21:43:27]

lgtm