blob: f4b8ff8ade83b13da43a3ad0e071fce88a40edb3 [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//
56// Paths can't contain NULs as a precaution agaist premature truncation.
57//
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:
86// The Open Group Base Specifications Issue 7, sections 3.266 ("Pathname")
87// and 4.12 ("Pathname Resolution"), available at:
88// http://www.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_266
89// 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>
106#include <string>
107#include <vector>
108
109#include "base/base_export.h"
110#include "base/compiler_specific.h"
brettw@chromium.org30230a82013-06-12 02:52:44 +0900111#include "base/containers/hash_tables.h"
avi@chromium.org94bd5732013-06-11 22:36:37 +0900112#include "base/strings/string16.h"
tfarina@chromium.orgb6d49112013-03-30 23:29:00 +0900113#include "base/strings/string_piece.h" // For implicit conversions.
brettw@chromium.org59eef1f2013-02-24 14:40:52 +0900114#include "build/build_config.h"
115
116// Windows-style drive letter support and pathname separator characters can be
117// enabled and disabled independently, to aid testing. These #defines are
118// here so that the same setting can be used in both the implementation and
119// in the unit test.
120#if defined(OS_WIN)
121#define FILE_PATH_USES_DRIVE_LETTERS
122#define FILE_PATH_USES_WIN_SEPARATORS
123#endif // OS_WIN
124
125class Pickle;
126class PickleIterator;
127
128namespace base {
129
130// An abstraction to isolate users from the differences between native
131// pathnames on different platforms.
132class BASE_EXPORT FilePath {
133 public:
134#if defined(OS_POSIX)
135 // On most platforms, native pathnames are char arrays, and the encoding
136 // may or may not be specified. On Mac OS X, native pathnames are encoded
137 // in UTF-8.
138 typedef std::string StringType;
139#elif defined(OS_WIN)
140 // On Windows, for Unicode-aware applications, native pathnames are wchar_t
141 // arrays encoded in UTF-16.
142 typedef std::wstring StringType;
143#endif // OS_WIN
144
145 typedef StringType::value_type CharType;
146
147 // Null-terminated array of separators used to separate components in
148 // hierarchical paths. Each character in this array is a valid separator,
149 // but kSeparators[0] is treated as the canonical separator and will be used
150 // when composing pathnames.
151 static const CharType kSeparators[];
152
scottmg@chromium.orgdef6ed82013-05-21 18:44:02 +0900153 // arraysize(kSeparators).
154 static const size_t kSeparatorsLength;
155
brettw@chromium.org59eef1f2013-02-24 14:40:52 +0900156 // A special path component meaning "this directory."
157 static const CharType kCurrentDirectory[];
158
159 // A special path component meaning "the parent directory."
160 static const CharType kParentDirectory[];
161
162 // The character used to identify a file extension.
163 static const CharType kExtensionSeparator;
164
165 FilePath();
166 FilePath(const FilePath& that);
167 explicit FilePath(const StringType& path);
168 ~FilePath();
169 FilePath& operator=(const FilePath& that);
170
171 bool operator==(const FilePath& that) const;
172
173 bool operator!=(const FilePath& that) const;
174
175 // Required for some STL containers and operations
176 bool operator<(const FilePath& that) const {
177 return path_ < that.path_;
178 }
179
180 const StringType& value() const { return path_; }
181
182 bool empty() const { return path_.empty(); }
183
184 void clear() { path_.clear(); }
185
186 // Returns true if |character| is in kSeparators.
187 static bool IsSeparator(CharType character);
188
189 // Returns a vector of all of the components of the provided path. It is
190 // equivalent to calling DirName().value() on the path's root component,
191 // and BaseName().value() on each child component.
192 void GetComponents(std::vector<FilePath::StringType>* components) const;
193
194 // Returns true if this FilePath is a strict parent of the |child|. Absolute
195 // and relative paths are accepted i.e. is /foo parent to /foo/bar and
196 // is foo parent to foo/bar. Does not convert paths to absolute, follow
197 // symlinks or directory navigation (e.g. ".."). A path is *NOT* its own
198 // parent.
199 bool IsParent(const FilePath& child) const;
200
201 // If IsParent(child) holds, appends to path (if non-NULL) the
202 // relative path to child and returns true. For example, if parent
203 // holds "/Users/johndoe/Library/Application Support", child holds
204 // "/Users/johndoe/Library/Application Support/Google/Chrome/Default", and
205 // *path holds "/Users/johndoe/Library/Caches", then after
206 // parent.AppendRelativePath(child, path) is called *path will hold
207 // "/Users/johndoe/Library/Caches/Google/Chrome/Default". Otherwise,
208 // returns false.
209 bool AppendRelativePath(const FilePath& child, FilePath* path) const;
210
211 // Returns a FilePath corresponding to the directory containing the path
212 // named by this object, stripping away the file component. If this object
213 // only contains one component, returns a FilePath identifying
214 // kCurrentDirectory. If this object already refers to the root directory,
215 // returns a FilePath identifying the root directory.
216 FilePath DirName() const WARN_UNUSED_RESULT;
217
218 // Returns a FilePath corresponding to the last path component of this
219 // object, either a file or a directory. If this object already refers to
220 // the root directory, returns a FilePath identifying the root directory;
221 // this is the only situation in which BaseName will return an absolute path.
222 FilePath BaseName() const WARN_UNUSED_RESULT;
223
224 // Returns ".jpg" for path "C:\pics\jojo.jpg", or an empty string if
225 // the file has no extension. If non-empty, Extension() will always start
226 // with precisely one ".". The following code should always work regardless
davidben@chromium.org64a720a2013-12-10 02:06:52 +0900227 // of the value of path. For common double-extensions like .tar.gz and
228 // .user.js, this method returns the combined extension. For a single
229 // component, use FinalExtension().
brettw@chromium.org59eef1f2013-02-24 14:40:52 +0900230 // new_path = path.RemoveExtension().value().append(path.Extension());
231 // ASSERT(new_path == path.value());
232 // NOTE: this is different from the original file_util implementation which
233 // returned the extension without a leading "." ("jpg" instead of ".jpg")
234 StringType Extension() const;
235
davidben@chromium.org64a720a2013-12-10 02:06:52 +0900236 // Returns the path's file extension, as in Extension(), but will
237 // never return a double extension.
238 //
239 // TODO(davidben): Check all our extension-sensitive code to see if
240 // we can rename this to Extension() and the other to something like
241 // LongExtension(), defaulting to short extensions and leaving the
242 // long "extensions" to logic like file_util::GetUniquePathNumber().
243 StringType FinalExtension() const;
244
brettw@chromium.org59eef1f2013-02-24 14:40:52 +0900245 // Returns "C:\pics\jojo" for path "C:\pics\jojo.jpg"
246 // NOTE: this is slightly different from the similar file_util implementation
247 // which returned simply 'jojo'.
248 FilePath RemoveExtension() const WARN_UNUSED_RESULT;
249
davidben@chromium.org64a720a2013-12-10 02:06:52 +0900250 // Removes the path's file extension, as in RemoveExtension(), but
251 // ignores double extensions.
252 FilePath RemoveFinalExtension() const WARN_UNUSED_RESULT;
253
brettw@chromium.org59eef1f2013-02-24 14:40:52 +0900254 // Inserts |suffix| after the file name portion of |path| but before the
255 // extension. Returns "" if BaseName() == "." or "..".
256 // Examples:
257 // path == "C:\pics\jojo.jpg" suffix == " (1)", returns "C:\pics\jojo (1).jpg"
258 // path == "jojo.jpg" suffix == " (1)", returns "jojo (1).jpg"
259 // path == "C:\pics\jojo" suffix == " (1)", returns "C:\pics\jojo (1)"
260 // path == "C:\pics.old\jojo" suffix == " (1)", returns "C:\pics.old\jojo (1)"
261 FilePath InsertBeforeExtension(
262 const StringType& suffix) const WARN_UNUSED_RESULT;
263 FilePath InsertBeforeExtensionASCII(
264 const base::StringPiece& suffix) const WARN_UNUSED_RESULT;
265
266 // Adds |extension| to |file_name|. Returns the current FilePath if
267 // |extension| is empty. Returns "" if BaseName() == "." or "..".
268 FilePath AddExtension(
269 const StringType& extension) const WARN_UNUSED_RESULT;
270
271 // Replaces the extension of |file_name| with |extension|. If |file_name|
272 // does not have an extension, then |extension| is added. If |extension| is
273 // empty, then the extension is removed from |file_name|.
274 // Returns "" if BaseName() == "." or "..".
275 FilePath ReplaceExtension(
276 const StringType& extension) const WARN_UNUSED_RESULT;
277
278 // Returns true if the file path matches the specified extension. The test is
279 // case insensitive. Don't forget the leading period if appropriate.
280 bool MatchesExtension(const StringType& extension) const;
281
282 // Returns a FilePath by appending a separator and the supplied path
283 // component to this object's path. Append takes care to avoid adding
284 // excessive separators if this object's path already ends with a separator.
285 // If this object's path is kCurrentDirectory, a new FilePath corresponding
286 // only to |component| is returned. |component| must be a relative path;
287 // it is an error to pass an absolute path.
288 FilePath Append(const StringType& component) const WARN_UNUSED_RESULT;
289 FilePath Append(const FilePath& component) const WARN_UNUSED_RESULT;
290
291 // Although Windows StringType is std::wstring, since the encoding it uses for
292 // paths is well defined, it can handle ASCII path components as well.
293 // Mac uses UTF8, and since ASCII is a subset of that, it works there as well.
294 // On Linux, although it can use any 8-bit encoding for paths, we assume that
295 // ASCII is a valid subset, regardless of the encoding, since many operating
296 // system paths will always be ASCII.
297 FilePath AppendASCII(const base::StringPiece& component)
298 const WARN_UNUSED_RESULT;
299
300 // Returns true if this FilePath contains an absolute path. On Windows, an
301 // absolute path begins with either a drive letter specification followed by
302 // a separator character, or with two separator characters. On POSIX
303 // platforms, an absolute path begins with a separator character.
304 bool IsAbsolute() const;
305
brettw@chromium.org99b198e2013-04-12 14:17:15 +0900306 // Returns true if the patch ends with a path separator character.
307 bool EndsWithSeparator() const WARN_UNUSED_RESULT;
308
309 // Returns a copy of this FilePath that ends with a trailing separator. If
310 // the input path is empty, an empty FilePath will be returned.
311 FilePath AsEndingWithSeparator() const WARN_UNUSED_RESULT;
312
brettw@chromium.org59eef1f2013-02-24 14:40:52 +0900313 // Returns a copy of this FilePath that does not end with a trailing
314 // separator.
315 FilePath StripTrailingSeparators() const WARN_UNUSED_RESULT;
316
317 // Returns true if this FilePath contains any attempt to reference a parent
318 // directory (i.e. has a path component that is ".."
319 bool ReferencesParent() const;
320
321 // Return a Unicode human-readable version of this path.
322 // Warning: you can *not*, in general, go from a display name back to a real
323 // path. Only use this when displaying paths to users, not just when you
324 // want to stuff a string16 into some other API.
325 string16 LossyDisplayName() const;
326
327 // Return the path as ASCII, or the empty string if the path is not ASCII.
328 // This should only be used for cases where the FilePath is representing a
329 // known-ASCII filename.
330 std::string MaybeAsASCII() const;
331
332 // Return the path as UTF-8.
333 //
334 // This function is *unsafe* as there is no way to tell what encoding is
335 // used in file names on POSIX systems other than Mac and Chrome OS,
336 // although UTF-8 is practically used everywhere these days. To mitigate
337 // the encoding issue, this function internally calls
338 // SysNativeMBToWide() on POSIX systems other than Mac and Chrome OS,
339 // per assumption that the current locale's encoding is used in file
340 // names, but this isn't a perfect solution.
341 //
342 // Once it becomes safe to to stop caring about non-UTF-8 file names,
343 // the SysNativeMBToWide() hack will be removed from the code, along
344 // with "Unsafe" in the function name.
345 std::string AsUTF8Unsafe() const;
346
darin@chromium.org1aead732013-06-21 06:29:54 +0900347 // Similar to AsUTF8Unsafe, but returns UTF-16 instead.
348 string16 AsUTF16Unsafe() const;
349
brettw@chromium.org59eef1f2013-02-24 14:40:52 +0900350 // Returns a FilePath object from a path name in UTF-8. This function
351 // should only be used for cases where you are sure that the input
352 // string is UTF-8.
353 //
354 // Like AsUTF8Unsafe(), this function is unsafe. This function
355 // internally calls SysWideToNativeMB() on POSIX systems other than Mac
356 // and Chrome OS, to mitigate the encoding issue. See the comment at
357 // AsUTF8Unsafe() for details.
358 static FilePath FromUTF8Unsafe(const std::string& utf8);
359
darin@chromium.org1aead732013-06-21 06:29:54 +0900360 // Similar to FromUTF8Unsafe, but accepts UTF-16 instead.
361 static FilePath FromUTF16Unsafe(const string16& utf16);
362
brettw@chromium.org59eef1f2013-02-24 14:40:52 +0900363 void WriteToPickle(Pickle* pickle) const;
364 bool ReadFromPickle(PickleIterator* iter);
365
366 // Normalize all path separators to backslash on Windows
367 // (if FILE_PATH_USES_WIN_SEPARATORS is true), or do nothing on POSIX systems.
368 FilePath NormalizePathSeparators() const;
369
370 // Compare two strings in the same way the file system does.
371 // Note that these always ignore case, even on file systems that are case-
372 // sensitive. If case-sensitive comparison is ever needed, add corresponding
373 // methods here.
374 // The methods are written as a static method so that they can also be used
375 // on parts of a file path, e.g., just the extension.
376 // CompareIgnoreCase() returns -1, 0 or 1 for less-than, equal-to and
377 // greater-than respectively.
378 static int CompareIgnoreCase(const StringType& string1,
379 const StringType& string2);
380 static bool CompareEqualIgnoreCase(const StringType& string1,
381 const StringType& string2) {
382 return CompareIgnoreCase(string1, string2) == 0;
383 }
384 static bool CompareLessIgnoreCase(const StringType& string1,
385 const StringType& string2) {
386 return CompareIgnoreCase(string1, string2) < 0;
387 }
388
389#if defined(OS_MACOSX)
390 // Returns the string in the special canonical decomposed form as defined for
391 // HFS, which is close to, but not quite, decomposition form D. See
392 // http://developer.apple.com/mac/library/technotes/tn/tn1150.html#UnicodeSubtleties
393 // for further comments.
394 // Returns the epmty string if the conversion failed.
395 static StringType GetHFSDecomposedForm(const FilePath::StringType& string);
396
397 // Special UTF-8 version of FastUnicodeCompare. Cf:
398 // http://developer.apple.com/mac/library/technotes/tn/tn1150.html#StringComparisonAlgorithm
399 // IMPORTANT: The input strings must be in the special HFS decomposed form!
400 // (cf. above GetHFSDecomposedForm method)
401 static int HFSFastUnicodeCompare(const StringType& string1,
402 const StringType& string2);
403#endif
404
qinmin@chromium.org8abcc0c2013-11-20 16:04:55 +0900405#if defined(OS_ANDROID)
406 // On android, file selection dialog can return a file with content uri
407 // scheme(starting with content://). Content uri needs to be opened with
408 // ContentResolver to guarantee that the app has appropriate permissions
409 // to access it.
410 // Returns true if the path is a content uri, or false otherwise.
411 bool IsContentUri() const;
412#endif
413
brettw@chromium.org59eef1f2013-02-24 14:40:52 +0900414 private:
415 // Remove trailing separators from this object. If the path is absolute, it
416 // will never be stripped any more than to refer to the absolute root
417 // directory, so "////" will become "/", not "". A leading pair of
418 // separators is never stripped, to support alternate roots. This is used to
419 // support UNC paths on Windows.
420 void StripTrailingSeparatorsInternal();
421
422 StringType path_;
423};
424
425} // namespace base
426
427// This is required by googletest to print a readable output on test failures.
428BASE_EXPORT extern void PrintTo(const base::FilePath& path, std::ostream* out);
429
430// Macros for string literal initialization of FilePath::CharType[], and for
431// using a FilePath::CharType[] in a printf-style format string.
432#if defined(OS_POSIX)
433#define FILE_PATH_LITERAL(x) x
434#define PRFilePath "s"
435#define PRFilePathLiteral "%s"
436#elif defined(OS_WIN)
437#define FILE_PATH_LITERAL(x) L ## x
438#define PRFilePath "ls"
439#define PRFilePathLiteral L"%ls"
440#endif // OS_WIN
441
442// Provide a hash function so that hash_sets and maps can contain FilePath
443// objects.
444namespace BASE_HASH_NAMESPACE {
445#if defined(COMPILER_GCC)
446
447template<>
448struct hash<base::FilePath> {
449 size_t operator()(const base::FilePath& f) const {
450 return hash<base::FilePath::StringType>()(f.value());
451 }
452};
453
454#elif defined(COMPILER_MSVC)
455
456inline size_t hash_value(const base::FilePath& f) {
457 return hash_value(f.value());
458}
459
460#endif // COMPILER
461
462} // namespace BASE_HASH_NAMESPACE
463
464#endif // BASE_FILES_FILE_PATH_H_