1 // 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[]           char16_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 char16_t[]-based
54 // pathnames on Windows.
55 //
56 // As a precaution against premature truncation, paths can't contain NULs.
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.267 ("Pathname")
87 //    and 4.12 ("Pathname Resolution"), available at:
88 //    http://www.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_267
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 
107 #include <iosfwd>
108 #include <string>
109 #include <string_view>
110 #include <vector>
111 
112 #include "base/compiler_specific.h"
113 #include "base/macros.h"
114 #include "util/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 
125 // To print path names portably use PRIsFP (based on PRIuS and friends from
126 // C99 and format_macros.h) like this:
127 // base::StringPrintf("Path is %" PRIsFP ".\n", PATH_CSTR(path);
128 #if defined(OS_WIN)
129 #define PRIsFP "ls"
130 #define PATH_CSTR(x) reinterpret_cast<const wchar_t*>(x.value().c_str())
131 #elif defined(OS_POSIX) || defined(OS_FUCHSIA)
132 #define PRIsFP "s"
133 #define PATH_CSTR(x) (x.value().c_str())
134 #endif  // OS_WIN
135 
136 namespace base {
137 
138 class Pickle;
139 class PickleIterator;
140 
141 // An abstraction to isolate users from the differences between native
142 // pathnames on different platforms.
143 class FilePath {
144  public:
145 #if defined(OS_WIN)
146   // On Windows, for Unicode-aware applications, native pathnames are char16_t
147   // arrays encoded in UTF-16.
148   typedef std::u16string StringType;
149 #elif defined(OS_POSIX) || defined(OS_FUCHSIA)
150   // On most platforms, native pathnames are char arrays, and the encoding
151   // may or may not be specified.  On Mac OS X, native pathnames are encoded
152   // in UTF-8.
153   typedef std::string StringType;
154 #endif  // OS_WIN
155 
156   using CharType = StringType::value_type;
157   using StringViewType = std::basic_string_view<CharType>;
158 
159   // Null-terminated array of separators used to separate components in
160   // hierarchical paths.  Each character in this array is a valid separator,
161   // but kSeparators[0] is treated as the canonical separator and will be used
162   // when composing pathnames.
163   static const CharType kSeparators[];
164 
165   // std::size(kSeparators).
166   static const size_t kSeparatorsLength;
167 
168   // A special path component meaning "this directory."
169   static const CharType kCurrentDirectory[];
170 
171   // A special path component meaning "the parent directory."
172   static const CharType kParentDirectory[];
173 
174   // The character used to identify a file extension.
175   static const CharType kExtensionSeparator;
176 
177   FilePath();
178   FilePath(const FilePath& that);
179   explicit FilePath(StringViewType path);
180   ~FilePath();
181   FilePath& operator=(const FilePath& that);
182 
183   // Constructs FilePath with the contents of |that|, which is left in valid but
184   // unspecified state.
185   FilePath(FilePath&& that) noexcept;
186   // Replaces the contents with those of |that|, which is left in valid but
187   // unspecified state.
188   FilePath& operator=(FilePath&& that);
189 
190   bool operator==(const FilePath& that) const;
191 
192   bool operator!=(const FilePath& that) const;
193 
194   // Required for some STL containers and operations
195   bool operator<(const FilePath& that) const { return path_ < that.path_; }
196 
value()197   const StringType& value() const { return path_; }
198 
empty()199   bool empty() const { return path_.empty(); }
200 
clear()201   void clear() { path_.clear(); }
202 
203   // Returns true if |character| is in kSeparators.
204   static bool IsSeparator(CharType character);
205 
206   // Returns a vector of all of the components of the provided path. It is
207   // equivalent to calling DirName().value() on the path's root component,
208   // and BaseName().value() on each child component.
209   //
210   // To make sure this is lossless so we can differentiate absolute and
211   // relative paths, the root slash will be included even though no other
212   // slashes will be. The precise behavior is:
213   //
214   // Posix:  "/foo/bar"  ->  [ "/", "foo", "bar" ]
215   // Windows:  "C:\foo\bar"  ->  [ "C:", "\\", "foo", "bar" ]
216   void GetComponents(std::vector<FilePath::StringType>* components) const;
217 
218   // Returns true if this FilePath is a strict parent of the |child|. Absolute
219   // and relative paths are accepted i.e. is /foo parent to /foo/bar and
220   // is foo parent to foo/bar. Does not convert paths to absolute, follow
221   // symlinks or directory navigation (e.g. ".."). A path is *NOT* its own
222   // parent.
223   bool IsParent(const FilePath& child) const;
224 
225   // If IsParent(child) holds, appends to path (if non-NULL) the
226   // relative path to child and returns true.  For example, if parent
227   // holds "/Users/johndoe/Library/Application Support", child holds
228   // "/Users/johndoe/Library/Application Support/Google/Chrome/Default", and
229   // *path holds "/Users/johndoe/Library/Caches", then after
230   // parent.AppendRelativePath(child, path) is called *path will hold
231   // "/Users/johndoe/Library/Caches/Google/Chrome/Default".  Otherwise,
232   // returns false.
233   bool AppendRelativePath(const FilePath& child, FilePath* path) const;
234 
235   // Returns a FilePath corresponding to the directory containing the path
236   // named by this object, stripping away the file component.  If this object
237   // only contains one component, returns a FilePath identifying
238   // kCurrentDirectory.  If this object already refers to the root directory,
239   // returns a FilePath identifying the root directory. Please note that this
240   // doesn't resolve directory navigation, e.g. the result for "../a" is "..".
241   FilePath DirName() const WARN_UNUSED_RESULT;
242 
243   // Returns a FilePath corresponding to the last path component of this
244   // object, either a file or a directory.  If this object already refers to
245   // the root directory, returns a FilePath identifying the root directory;
246   // this is the only situation in which BaseName will return an absolute path.
247   FilePath BaseName() const WARN_UNUSED_RESULT;
248 
249   // Returns ".jpg" for path "C:\pics\jojo.jpg", or an empty string if
250   // the file has no extension.  If non-empty, Extension() will always start
251   // with precisely one ".".  The following code should always work regardless
252   // of the value of path.  For common double-extensions like .tar.gz and
253   // .user.js, this method returns the combined extension.  For a single
254   // component, use FinalExtension().
255   // new_path = path.RemoveExtension().value().append(path.Extension());
256   // ASSERT(new_path == path.value());
257   // NOTE: this is different from the original file_util implementation which
258   // returned the extension without a leading "." ("jpg" instead of ".jpg")
259   StringType Extension() const WARN_UNUSED_RESULT;
260 
261   // Returns the path's file extension, as in Extension(), but will
262   // never return a double extension.
263   //
264   // TODO(davidben): Check all our extension-sensitive code to see if
265   // we can rename this to Extension() and the other to something like
266   // LongExtension(), defaulting to short extensions and leaving the
267   // long "extensions" to logic like base::GetUniquePathNumber().
268   StringType FinalExtension() const WARN_UNUSED_RESULT;
269 
270   // Returns "C:\pics\jojo" for path "C:\pics\jojo.jpg"
271   // NOTE: this is slightly different from the similar file_util implementation
272   // which returned simply 'jojo'.
273   FilePath RemoveExtension() const WARN_UNUSED_RESULT;
274 
275   // Removes the path's file extension, as in RemoveExtension(), but
276   // ignores double extensions.
277   FilePath RemoveFinalExtension() const WARN_UNUSED_RESULT;
278 
279   // Inserts |suffix| after the file name portion of |path| but before the
280   // extension.  Returns "" if BaseName() == "." or "..".
281   // Examples:
282   // path == "C:\pics\jojo.jpg" suffix == " (1)", returns "C:\pics\jojo (1).jpg"
283   // path == "jojo.jpg"         suffix == " (1)", returns "jojo (1).jpg"
284   // path == "C:\pics\jojo"     suffix == " (1)", returns "C:\pics\jojo (1)"
285   // path == "C:\pics.old\jojo" suffix == " (1)", returns "C:\pics.old\jojo (1)"
286   FilePath InsertBeforeExtension(StringViewType suffix) const
287       WARN_UNUSED_RESULT;
288   FilePath InsertBeforeExtensionASCII(std::string_view suffix) const
289       WARN_UNUSED_RESULT;
290 
291   // Adds |extension| to |file_name|. Returns the current FilePath if
292   // |extension| is empty. Returns "" if BaseName() == "." or "..".
293   FilePath AddExtension(StringViewType extension) const WARN_UNUSED_RESULT;
294 
295   // Replaces the extension of |file_name| with |extension|.  If |file_name|
296   // does not have an extension, then |extension| is added.  If |extension| is
297   // empty, then the extension is removed from |file_name|.
298   // Returns "" if BaseName() == "." or "..".
299   FilePath ReplaceExtension(StringViewType extension) const WARN_UNUSED_RESULT;
300 
301   // Returns a FilePath by appending a separator and the supplied path
302   // component to this object's path.  Append takes care to avoid adding
303   // excessive separators if this object's path already ends with a separator.
304   // If this object's path is kCurrentDirectory, a new FilePath corresponding
305   // only to |component| is returned.  |component| must be a relative path;
306   // it is an error to pass an absolute path.
307   FilePath Append(StringViewType component) const WARN_UNUSED_RESULT;
308   FilePath Append(const FilePath& component) const WARN_UNUSED_RESULT;
309 
310   // Although Windows StringType is std::u16string, since the encoding it uses
311   // for paths is well defined, it can handle ASCII path components as well. Mac
312   // uses UTF8, and since ASCII is a subset of that, it works there as well. On
313   // Linux, although it can use any 8-bit encoding for paths, we assume that
314   // ASCII is a valid subset, regardless of the encoding, since many operating
315   // system paths will always be ASCII.
316   FilePath AppendASCII(std::string_view component) const WARN_UNUSED_RESULT;
317 
318   // Returns true if this FilePath contains an absolute path.  On Windows, an
319   // absolute path begins with either a drive letter specification followed by
320   // a separator character, or with two separator characters.  On POSIX
321   // platforms, an absolute path begins with a separator character.
322   bool IsAbsolute() const;
323 
324   // Returns true if the patch ends with a path separator character.
325   bool EndsWithSeparator() const WARN_UNUSED_RESULT;
326 
327   // Returns a copy of this FilePath that ends with a trailing separator. If
328   // the input path is empty, an empty FilePath will be returned.
329   FilePath AsEndingWithSeparator() const WARN_UNUSED_RESULT;
330 
331   // Returns a copy of this FilePath that does not end with a trailing
332   // separator.
333   FilePath StripTrailingSeparators() const WARN_UNUSED_RESULT;
334 
335   // Returns true if this FilePath contains an attempt to reference a parent
336   // directory (e.g. has a path component that is "..").
337   bool ReferencesParent() const;
338 
339   // Return a Unicode human-readable version of this path.
340   // Warning: you can *not*, in general, go from a display name back to a real
341   // path.  Only use this when displaying paths to users, not just when you
342   // want to stuff a std::u16string into some other API.
343   std::u16string LossyDisplayName() const;
344 
345   // Return the path as ASCII, or the empty string if the path is not ASCII.
346   // This should only be used for cases where the FilePath is representing a
347   // known-ASCII filename.
348   std::string MaybeAsASCII() const;
349 
350   // Return the path as 8-bit. On Linux this isn't guaranteed to be UTF-8.
351   std::string As8Bit() const;
352 
353   // Normalize all path separators to backslash on Windows
354   // (if FILE_PATH_USES_WIN_SEPARATORS is true), or do nothing on POSIX systems.
355   FilePath NormalizePathSeparators() const;
356 
357   // Normalize all path separattors to given type on Windows
358   // (if FILE_PATH_USES_WIN_SEPARATORS is true), or do nothing on POSIX systems.
359   FilePath NormalizePathSeparatorsTo(CharType separator) const;
360 
361  private:
362   // Remove trailing separators from this object.  If the path is absolute, it
363   // will never be stripped any more than to refer to the absolute root
364   // directory, so "////" will become "/", not "".  A leading pair of
365   // separators is never stripped, to support alternate roots.  This is used to
366   // support UNC paths on Windows.
367   void StripTrailingSeparatorsInternal();
368 
369   StringType path_;
370 };
371 
372 }  // namespace base
373 
374 // Macros for string literal initialization of FilePath::CharType[].
375 #if defined(OS_WIN)
376 #define FILE_PATH_LITERAL(x) u##x
377 #elif defined(OS_POSIX) || defined(OS_FUCHSIA)
378 #define FILE_PATH_LITERAL(x) x
379 #endif  // OS_WIN
380 
381 namespace std {
382 
383 template <>
384 struct hash<base::FilePath> {
385   typedef base::FilePath argument_type;
386   typedef std::size_t result_type;
387   result_type operator()(argument_type const& f) const {
388     return hash<base::FilePath::StringType>()(f.value());
389   }
390 };
391 
392 }  // namespace std
393 
394 #endif  // BASE_FILES_FILE_PATH_H_
395