Add our own (mojo::util::)ScopedFILE and replace uses of base::ScopedFILE with it.

Add our own (mojo::util::)ScopedFILE and replace uses of base::ScopedFILE with it.

It's entirely equivalent to base::ScopedFILE. For now, we continue to
use base's scoped_ptr, but we could use std::unique_ptr instead in the
future.

R=vardhan@google.com

Committed: https://chromium.googlesource.com/external/mojo/+/9108b3c3359fc3f2b08094a1a53327f1227c3bea

[vardhan, 2015-09-15 21:48:29]

lgtm

https://codereview.chromium.org/1347783002/diff/1/mojo/edk/system/BUILD.gn
File mojo/edk/system/BUILD.gn (right):

https://codereview.chromium.org/1347783002/diff/1/mojo/edk/system/BUILD.gn#ne...
mojo/edk/system/BUILD.gn:222: "../util",
I think it might be safer to use absolute paths for targets instead of relative?
 But I guess this is not followed anywhere else, so I guess I'm just looking for
your opinion.

[viettrungluu, 2015-09-15 21:51:13]

On 2015/09/15 21:48:29, vardhan wrote:
> lgtm
> 
> https://codereview.chromium.org/1347783002/diff/1/mojo/edk/system/BUILD.gn
> File mojo/edk/system/BUILD.gn (right):
> 
>
https://codereview.chromium.org/1347783002/diff/1/mojo/edk/system/BUILD.gn#ne...
> mojo/edk/system/BUILD.gn:222: "../util",
> I think it might be safer to use absolute paths for targets instead of
relative?
>  But I guess this is not followed anywhere else, so I guess I'm just looking
for
> your opinion.

In the EDK, which may be placed in some other subdirectory, relative paths are
needed. There are also mojo_edk_... target types with mojo_edk... variables that
automatically rewrite paths. (See also
https://github.com/domokit/mojo/issues/421 .)

[viettrungluu, 2015-09-15 21:52:03]

Committed patchset #1 (id:1) manually as
9108b3c3359fc3f2b08094a1a53327f1227c3bea (presubmit successful).