blob: 3a0513d93b316ed08dd647ace19130e8aefe3f54 [file] [log] [blame]
brettw@chromium.org59eef1f2013-02-24 14:40:52 +09001// Copyright (c) 2012 The Chromium Authors. All rights reserved.
2// Use of this source code is governed by a BSD-style license that can be
3// found in the LICENSE file.
4
5// FilePath is a container for pathnames stored in a platform's native string
6// type, providing containers for manipulation in according with the
7// platform's conventions for pathnames. It supports the following path
8// types:
9//
10// POSIX Windows
11// --------------- ----------------------------------
12// Fundamental type char[] wchar_t[]
13// Encoding unspecified* UTF-16
14// Separator / \, tolerant of /
15// Drive letters no case-insensitive A-Z followed by :
16// Alternate root // (surprise!) \\, for UNC paths
17//
18// * The encoding need not be specified on POSIX systems, although some
19// POSIX-compliant systems do specify an encoding. Mac OS X uses UTF-8.
20// Chrome OS also uses UTF-8.
21// Linux does not specify an encoding, but in practice, the locale's
22// character set may be used.
23//
24// For more arcane bits of path trivia, see below.
25//
26// FilePath objects are intended to be used anywhere paths are. An
27// application may pass FilePath objects around internally, masking the
28// underlying differences between systems, only differing in implementation
29// where interfacing directly with the system. For example, a single
30// OpenFile(const FilePath &) function may be made available, allowing all
31// callers to operate without regard to the underlying implementation. On
32// POSIX-like platforms, OpenFile might wrap fopen, and on Windows, it might
33// wrap _wfopen_s, perhaps both by calling file_path.value().c_str(). This
34// allows each platform to pass pathnames around without requiring conversions
35// between encodings, which has an impact on performance, but more imporantly,
36// has an impact on correctness on platforms that do not have well-defined
37// encodings for pathnames.
38//
39// Several methods are available to perform common operations on a FilePath
40// object, such as determining the parent directory (DirName), isolating the
41// final path component (BaseName), and appending a relative pathname string
42// to an existing FilePath object (Append). These methods are highly
43// recommended over attempting to split and concatenate strings directly.
44// These methods are based purely on string manipulation and knowledge of
45// platform-specific pathname conventions, and do not consult the filesystem
46// at all, making them safe to use without fear of blocking on I/O operations.
47// These methods do not function as mutators but instead return distinct
48// instances of FilePath objects, and are therefore safe to use on const
49// objects. The objects themselves are safe to share between threads.
50//
51// To aid in initialization of FilePath objects from string literals, a
52// FILE_PATH_LITERAL macro is provided, which accounts for the difference
53// between char[]-based pathnames on POSIX systems and wchar_t[]-based
54// pathnames on Windows.
55//
dougk2e9fe272015-02-13 11:47:52 +090056// As a precaution against premature truncation, paths can't contain NULs.
brettw@chromium.org59eef1f2013-02-24 14:40:52 +090057//
58// Because a FilePath object should not be instantiated at the global scope,
59// instead, use a FilePath::CharType[] and initialize it with
60// FILE_PATH_LITERAL. At runtime, a FilePath object can be created from the
61// character array. Example:
62//
63// | const FilePath::CharType kLogFileName[] = FILE_PATH_LITERAL("log.txt");
64// |
65// | void Function() {
66// | FilePath log_file_path(kLogFileName);
67// | [...]
68// | }
69//
70// WARNING: FilePaths should ALWAYS be displayed with LTR directionality, even
71// when the UI language is RTL. This means you always need to pass filepaths
72// through base::i18n::WrapPathWithLTRFormatting() before displaying it in the
73// RTL UI.
74//
75// This is a very common source of bugs, please try to keep this in mind.
76//
77// ARCANE BITS OF PATH TRIVIA
78//
79// - A double leading slash is actually part of the POSIX standard. Systems
80// are allowed to treat // as an alternate root, as Windows does for UNC
81// (network share) paths. Most POSIX systems don't do anything special
82// with two leading slashes, but FilePath handles this case properly
83// in case it ever comes across such a system. FilePath needs this support
84// for Windows UNC paths, anyway.
85// References:
dougk2e9fe272015-02-13 11:47:52 +090086// The Open Group Base Specifications Issue 7, sections 3.267 ("Pathname")
brettw@chromium.org59eef1f2013-02-24 14:40:52 +090087// and 4.12 ("Pathname Resolution"), available at:
dougk2e9fe272015-02-13 11:47:52 +090088// http://www.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_267
brettw@chromium.org59eef1f2013-02-24 14:40:52 +090089// http://www.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap04.html#tag_04_12
90//
91// - Windows treats c:\\ the same way it treats \\. This was intended to
92// allow older applications that require drive letters to support UNC paths
93// like \\server\share\path, by permitting c:\\server\share\path as an
94// equivalent. Since the OS treats these paths specially, FilePath needs
95// to do the same. Since Windows can use either / or \ as the separator,
96// FilePath treats c://, c:\\, //, and \\ all equivalently.
97// Reference:
98// The Old New Thing, "Why is a drive letter permitted in front of UNC
99// paths (sometimes)?", available at:
100// http://blogs.msdn.com/oldnewthing/archive/2005/11/22/495740.aspx
101
102#ifndef BASE_FILES_FILE_PATH_H_
103#define BASE_FILES_FILE_PATH_H_
104
105#include <stddef.h>
mgiuca36c0d632015-05-28 19:11:33 +0900106
107#include <iosfwd>
brettw@chromium.org59eef1f2013-02-24 14:40:52 +0900108#include <string>
109#include <vector>
110
111#include "base/base_export.h"
pkastingee4b1122014-11-21 10:37:22 +0900112#include "base/compiler_specific.h"
brettw@chromium.org30230a82013-06-12 02:52:44 +0900113#include "base/containers/hash_tables.h"
avi@chromium.org94bd5732013-06-11 22:36:37 +0900114#include "base/strings/string16.h"
tfarina@chromium.orgb6d49112013-03-30 23:29:00 +0900115#include "base/strings/string_piece.h" // For implicit conversions.
brettw@chromium.org59eef1f2013-02-24 14:40:52 +0900116#include "build/build_config.h"
117
118// Windows-style drive letter support and pathname separator characters can be
119// enabled and disabled independently, to aid testing. These #defines are
120// here so that the same setting can be used in both the implementation and
121// in the unit test.
122#if defined(OS_WIN)
123#define FILE_PATH_USES_DRIVE_LETTERS
124#define FILE_PATH_USES_WIN_SEPARATORS
125#endif // OS_WIN
126
127class Pickle;
128class PickleIterator;
129
130namespace base {
131
132// An abstraction to isolate users from the differences between native
133// pathnames on different platforms.
134class BASE_EXPORT FilePath {
135 public:
136#if defined(OS_POSIX)
137 // On most platforms, native pathnames are char arrays, and the encoding
138 // may or may not be specified. On Mac OS X, native pathnames are encoded
139 // in UTF-8.
140 typedef std::string StringType;
141#elif defined(OS_WIN)
142 // On Windows, for Unicode-aware applications, native pathnames are wchar_t
143 // arrays encoded in UTF-16.
144 typedef std::wstring StringType;
145#endif // OS_WIN
146
147 typedef StringType::value_type CharType;
148
149 // Null-terminated array of separators used to separate components in
150 // hierarchical paths. Each character in this array is a valid separator,
151 // but kSeparators[0] is treated as the canonical separator and will be used
152 // when composing pathnames.
153 static const CharType kSeparators[];
154
scottmg@chromium.orgdef6ed82013-05-21 18:44:02 +0900155 // arraysize(kSeparators).
156 static const size_t kSeparatorsLength;
157
brettw@chromium.org59eef1f2013-02-24 14:40:52 +0900158 // A special path component meaning "this directory."
159 static const CharType kCurrentDirectory[];
160
161 // A special path component meaning "the parent directory."
162 static const CharType kParentDirectory[];
163
164 // The character used to identify a file extension.
165 static const CharType kExtensionSeparator;
166
167 FilePath();
168 FilePath(const FilePath& that);
169 explicit FilePath(const StringType& path);
170 ~FilePath();
171 FilePath& operator=(const FilePath& that);
172
173 bool operator==(const FilePath& that) const;
174
175 bool operator!=(const FilePath& that) const;
176
177 // Required for some STL containers and operations
178 bool operator<(const FilePath& that) const {
179 return path_ < that.path_;
180 }
181
182 const StringType& value() const { return path_; }
183
184 bool empty() const { return path_.empty(); }
185
186 void clear() { path_.clear(); }
187
188 // Returns true if |character| is in kSeparators.
189 static bool IsSeparator(CharType character);
190
191 // Returns a vector of all of the components of the provided path. It is
192 // equivalent to calling DirName().value() on the path's root component,
193 // and BaseName().value() on each child component.
brettw@chromium.orgb80e1ef2014-02-20 04:11:17 +0900194 //
195 // To make sure this is lossless so we can differentiate absolute and
196 // relative paths, the root slash will be included even though no other
197 // slashes will be. The precise behavior is:
198 //
199 // Posix: "/foo/bar" -> [ "/", "foo", "bar" ]
200 // Windows: "C:\foo\bar" -> [ "C:", "\\", "foo", "bar" ]
brettw@chromium.org59eef1f2013-02-24 14:40:52 +0900201 void GetComponents(std::vector<FilePath::StringType>* components) const;
202
203 // Returns true if this FilePath is a strict parent of the |child|. Absolute
204 // and relative paths are accepted i.e. is /foo parent to /foo/bar and
205 // is foo parent to foo/bar. Does not convert paths to absolute, follow
206 // symlinks or directory navigation (e.g. ".."). A path is *NOT* its own
207 // parent.
208 bool IsParent(const FilePath& child) const;
209
210 // If IsParent(child) holds, appends to path (if non-NULL) the
211 // relative path to child and returns true. For example, if parent
212 // holds "/Users/johndoe/Library/Application Support", child holds
213 // "/Users/johndoe/Library/Application Support/Google/Chrome/Default", and
214 // *path holds "/Users/johndoe/Library/Caches", then after
215 // parent.AppendRelativePath(child, path) is called *path will hold
216 // "/Users/johndoe/Library/Caches/Google/Chrome/Default". Otherwise,
217 // returns false.
218 bool AppendRelativePath(const FilePath& child, FilePath* path) const;
219
220 // Returns a FilePath corresponding to the directory containing the path
221 // named by this object, stripping away the file component. If this object
222 // only contains one component, returns a FilePath identifying
223 // kCurrentDirectory. If this object already refers to the root directory,
224 // returns a FilePath identifying the root directory.
225 FilePath DirName() const WARN_UNUSED_RESULT;
226
227 // Returns a FilePath corresponding to the last path component of this
228 // object, either a file or a directory. If this object already refers to
229 // the root directory, returns a FilePath identifying the root directory;
230 // this is the only situation in which BaseName will return an absolute path.
231 FilePath BaseName() const WARN_UNUSED_RESULT;
232
233 // Returns ".jpg" for path "C:\pics\jojo.jpg", or an empty string if
234 // the file has no extension. If non-empty, Extension() will always start
235 // with precisely one ".". The following code should always work regardless
davidben@chromium.org64a720a2013-12-10 02:06:52 +0900236 // of the value of path. For common double-extensions like .tar.gz and
237 // .user.js, this method returns the combined extension. For a single
238 // component, use FinalExtension().
brettw@chromium.org59eef1f2013-02-24 14:40:52 +0900239 // new_path = path.RemoveExtension().value().append(path.Extension());
240 // ASSERT(new_path == path.value());
241 // NOTE: this is different from the original file_util implementation which
242 // returned the extension without a leading "." ("jpg" instead of ".jpg")
scottmg624fe102015-01-21 04:15:54 +0900243 StringType Extension() const WARN_UNUSED_RESULT;
brettw@chromium.org59eef1f2013-02-24 14:40:52 +0900244
davidben@chromium.org64a720a2013-12-10 02:06:52 +0900245 // Returns the path's file extension, as in Extension(), but will
246 // never return a double extension.
247 //
248 // TODO(davidben): Check all our extension-sensitive code to see if
249 // we can rename this to Extension() and the other to something like
250 // LongExtension(), defaulting to short extensions and leaving the
brettw@chromium.orgaa82a772014-03-14 02:26:21 +0900251 // long "extensions" to logic like base::GetUniquePathNumber().
scottmg624fe102015-01-21 04:15:54 +0900252 StringType FinalExtension() const WARN_UNUSED_RESULT;
davidben@chromium.org64a720a2013-12-10 02:06:52 +0900253
brettw@chromium.org59eef1f2013-02-24 14:40:52 +0900254 // Returns "C:\pics\jojo" for path "C:\pics\jojo.jpg"
255 // NOTE: this is slightly different from the similar file_util implementation
256 // which returned simply 'jojo'.
257 FilePath RemoveExtension() const WARN_UNUSED_RESULT;
258
davidben@chromium.org64a720a2013-12-10 02:06:52 +0900259 // Removes the path's file extension, as in RemoveExtension(), but
260 // ignores double extensions.
261 FilePath RemoveFinalExtension() const WARN_UNUSED_RESULT;
262
brettw@chromium.org59eef1f2013-02-24 14:40:52 +0900263 // Inserts |suffix| after the file name portion of |path| but before the
264 // extension. Returns "" if BaseName() == "." or "..".
265 // Examples:
266 // path == "C:\pics\jojo.jpg" suffix == " (1)", returns "C:\pics\jojo (1).jpg"
267 // path == "jojo.jpg" suffix == " (1)", returns "jojo (1).jpg"
268 // path == "C:\pics\jojo" suffix == " (1)", returns "C:\pics\jojo (1)"
269 // path == "C:\pics.old\jojo" suffix == " (1)", returns "C:\pics.old\jojo (1)"
270 FilePath InsertBeforeExtension(
271 const StringType& suffix) const WARN_UNUSED_RESULT;
272 FilePath InsertBeforeExtensionASCII(
273 const base::StringPiece& suffix) const WARN_UNUSED_RESULT;
274
275 // Adds |extension| to |file_name|. Returns the current FilePath if
276 // |extension| is empty. Returns "" if BaseName() == "." or "..".
277 FilePath AddExtension(
278 const StringType& extension) const WARN_UNUSED_RESULT;
279
280 // Replaces the extension of |file_name| with |extension|. If |file_name|
281 // does not have an extension, then |extension| is added. If |extension| is
282 // empty, then the extension is removed from |file_name|.
283 // Returns "" if BaseName() == "." or "..".
284 FilePath ReplaceExtension(
285 const StringType& extension) const WARN_UNUSED_RESULT;
286
287 // Returns true if the file path matches the specified extension. The test is
288 // case insensitive. Don't forget the leading period if appropriate.
289 bool MatchesExtension(const StringType& extension) const;
290
291 // Returns a FilePath by appending a separator and the supplied path
292 // component to this object's path. Append takes care to avoid adding
293 // excessive separators if this object's path already ends with a separator.
294 // If this object's path is kCurrentDirectory, a new FilePath corresponding
295 // only to |component| is returned. |component| must be a relative path;
296 // it is an error to pass an absolute path.
297 FilePath Append(const StringType& component) const WARN_UNUSED_RESULT;
298 FilePath Append(const FilePath& component) const WARN_UNUSED_RESULT;
299
300 // Although Windows StringType is std::wstring, since the encoding it uses for
301 // paths is well defined, it can handle ASCII path components as well.
302 // Mac uses UTF8, and since ASCII is a subset of that, it works there as well.
303 // On Linux, although it can use any 8-bit encoding for paths, we assume that
304 // ASCII is a valid subset, regardless of the encoding, since many operating
305 // system paths will always be ASCII.
306 FilePath AppendASCII(const base::StringPiece& component)
307 const WARN_UNUSED_RESULT;
308
309 // Returns true if this FilePath contains an absolute path. On Windows, an
310 // absolute path begins with either a drive letter specification followed by
311 // a separator character, or with two separator characters. On POSIX
312 // platforms, an absolute path begins with a separator character.
313 bool IsAbsolute() const;
314
brettw@chromium.org99b198e2013-04-12 14:17:15 +0900315 // Returns true if the patch ends with a path separator character.
316 bool EndsWithSeparator() const WARN_UNUSED_RESULT;
317
318 // Returns a copy of this FilePath that ends with a trailing separator. If
319 // the input path is empty, an empty FilePath will be returned.
320 FilePath AsEndingWithSeparator() const WARN_UNUSED_RESULT;
321
brettw@chromium.org59eef1f2013-02-24 14:40:52 +0900322 // Returns a copy of this FilePath that does not end with a trailing
323 // separator.
324 FilePath StripTrailingSeparators() const WARN_UNUSED_RESULT;
325
tnagel@chromium.orge2352822014-05-02 01:52:07 +0900326 // Returns true if this FilePath contains an attempt to reference a parent
327 // directory (e.g. has a path component that is "..").
brettw@chromium.org59eef1f2013-02-24 14:40:52 +0900328 bool ReferencesParent() const;
329
330 // Return a Unicode human-readable version of this path.
331 // Warning: you can *not*, in general, go from a display name back to a real
332 // path. Only use this when displaying paths to users, not just when you
333 // want to stuff a string16 into some other API.
334 string16 LossyDisplayName() const;
335
336 // Return the path as ASCII, or the empty string if the path is not ASCII.
337 // This should only be used for cases where the FilePath is representing a
338 // known-ASCII filename.
339 std::string MaybeAsASCII() const;
340
341 // Return the path as UTF-8.
342 //
343 // This function is *unsafe* as there is no way to tell what encoding is
344 // used in file names on POSIX systems other than Mac and Chrome OS,
345 // although UTF-8 is practically used everywhere these days. To mitigate
346 // the encoding issue, this function internally calls
347 // SysNativeMBToWide() on POSIX systems other than Mac and Chrome OS,
348 // per assumption that the current locale's encoding is used in file
349 // names, but this isn't a perfect solution.
350 //
351 // Once it becomes safe to to stop caring about non-UTF-8 file names,
352 // the SysNativeMBToWide() hack will be removed from the code, along
353 // with "Unsafe" in the function name.
354 std::string AsUTF8Unsafe() const;
355
darin@chromium.org1aead732013-06-21 06:29:54 +0900356 // Similar to AsUTF8Unsafe, but returns UTF-16 instead.
357 string16 AsUTF16Unsafe() const;
358
brettw@chromium.org59eef1f2013-02-24 14:40:52 +0900359 // Returns a FilePath object from a path name in UTF-8. This function
360 // should only be used for cases where you are sure that the input
361 // string is UTF-8.
362 //
363 // Like AsUTF8Unsafe(), this function is unsafe. This function
364 // internally calls SysWideToNativeMB() on POSIX systems other than Mac
365 // and Chrome OS, to mitigate the encoding issue. See the comment at
366 // AsUTF8Unsafe() for details.
367 static FilePath FromUTF8Unsafe(const std::string& utf8);
368
darin@chromium.org1aead732013-06-21 06:29:54 +0900369 // Similar to FromUTF8Unsafe, but accepts UTF-16 instead.
370 static FilePath FromUTF16Unsafe(const string16& utf16);
371
brettw@chromium.org59eef1f2013-02-24 14:40:52 +0900372 void WriteToPickle(Pickle* pickle) const;
373 bool ReadFromPickle(PickleIterator* iter);
374
375 // Normalize all path separators to backslash on Windows
376 // (if FILE_PATH_USES_WIN_SEPARATORS is true), or do nothing on POSIX systems.
377 FilePath NormalizePathSeparators() const;
378
scottmg@chromium.orgb58eb012014-04-03 16:45:42 +0900379 // Normalize all path separattors to given type on Windows
380 // (if FILE_PATH_USES_WIN_SEPARATORS is true), or do nothing on POSIX systems.
381 FilePath NormalizePathSeparatorsTo(CharType separator) const;
382
brettw@chromium.org59eef1f2013-02-24 14:40:52 +0900383 // Compare two strings in the same way the file system does.
384 // Note that these always ignore case, even on file systems that are case-
385 // sensitive. If case-sensitive comparison is ever needed, add corresponding
386 // methods here.
387 // The methods are written as a static method so that they can also be used
388 // on parts of a file path, e.g., just the extension.
389 // CompareIgnoreCase() returns -1, 0 or 1 for less-than, equal-to and
390 // greater-than respectively.
391 static int CompareIgnoreCase(const StringType& string1,
392 const StringType& string2);
393 static bool CompareEqualIgnoreCase(const StringType& string1,
394 const StringType& string2) {
395 return CompareIgnoreCase(string1, string2) == 0;
396 }
397 static bool CompareLessIgnoreCase(const StringType& string1,
398 const StringType& string2) {
399 return CompareIgnoreCase(string1, string2) < 0;
400 }
401
402#if defined(OS_MACOSX)
403 // Returns the string in the special canonical decomposed form as defined for
404 // HFS, which is close to, but not quite, decomposition form D. See
405 // http://developer.apple.com/mac/library/technotes/tn/tn1150.html#UnicodeSubtleties
406 // for further comments.
407 // Returns the epmty string if the conversion failed.
408 static StringType GetHFSDecomposedForm(const FilePath::StringType& string);
409
410 // Special UTF-8 version of FastUnicodeCompare. Cf:
411 // http://developer.apple.com/mac/library/technotes/tn/tn1150.html#StringComparisonAlgorithm
412 // IMPORTANT: The input strings must be in the special HFS decomposed form!
413 // (cf. above GetHFSDecomposedForm method)
414 static int HFSFastUnicodeCompare(const StringType& string1,
415 const StringType& string2);
416#endif
417
qinmin@chromium.org8abcc0c2013-11-20 16:04:55 +0900418#if defined(OS_ANDROID)
419 // On android, file selection dialog can return a file with content uri
420 // scheme(starting with content://). Content uri needs to be opened with
421 // ContentResolver to guarantee that the app has appropriate permissions
422 // to access it.
423 // Returns true if the path is a content uri, or false otherwise.
424 bool IsContentUri() const;
425#endif
426
brettw@chromium.org59eef1f2013-02-24 14:40:52 +0900427 private:
428 // Remove trailing separators from this object. If the path is absolute, it
429 // will never be stripped any more than to refer to the absolute root
430 // directory, so "////" will become "/", not "". A leading pair of
431 // separators is never stripped, to support alternate roots. This is used to
432 // support UNC paths on Windows.
433 void StripTrailingSeparatorsInternal();
434
435 StringType path_;
436};
437
brettw@chromium.org59eef1f2013-02-24 14:40:52 +0900438// This is required by googletest to print a readable output on test failures.
mgiuca36c0d632015-05-28 19:11:33 +0900439// This is declared here for use in gtest-based unit tests but is defined in
440// the test_support_base target. Depend on that to use this in your unit test.
441// This should not be used in production code - call ToString() instead.
442void PrintTo(const FilePath& path, std::ostream* out);
443
444} // namespace base
brettw@chromium.org59eef1f2013-02-24 14:40:52 +0900445
446// Macros for string literal initialization of FilePath::CharType[], and for
447// using a FilePath::CharType[] in a printf-style format string.
448#if defined(OS_POSIX)
449#define FILE_PATH_LITERAL(x) x
450#define PRFilePath "s"
brettw@chromium.org59eef1f2013-02-24 14:40:52 +0900451#elif defined(OS_WIN)
452#define FILE_PATH_LITERAL(x) L ## x
453#define PRFilePath "ls"
brettw@chromium.org59eef1f2013-02-24 14:40:52 +0900454#endif // OS_WIN
455
456// Provide a hash function so that hash_sets and maps can contain FilePath
457// objects.
458namespace BASE_HASH_NAMESPACE {
brettw@chromium.org59eef1f2013-02-24 14:40:52 +0900459
460template<>
461struct hash<base::FilePath> {
462 size_t operator()(const base::FilePath& f) const {
463 return hash<base::FilePath::StringType>()(f.value());
464 }
465};
466
brettw@chromium.org59eef1f2013-02-24 14:40:52 +0900467} // namespace BASE_HASH_NAMESPACE
468
469#endif // BASE_FILES_FILE_PATH_H_