From 8bb9ae92ad0721adca944d8a8197f3e5d3944bd6 Mon Sep 17 00:00:00 2001
From: Max Horn
Date: Wed, 26 Apr 2006 08:29:32 +0000
Subject: Yet another revision of File::exists. I now believe the function
 really is 'wrong' right now (it has to fulfill too many roles right now).
 Need to correctly fix this later

svn-id: r22171
---
 common/file.cpp | 28 +++++++++++++++++++++++++++-
 1 file changed, 27 insertions(+), 1 deletion(-)

(limited to 'common')

diff --git a/common/file.cpp b/common/file.cpp
index 90acdb45d3..267b993276 100644
--- a/common/file.cpp
+++ b/common/file.cpp
@@ -263,8 +263,34 @@ bool File::open(const String &filename, AccessMode mode, const char *directory)
 }
 
 bool File::exists(const String &filename) {
+	// First try to find the file it via a FilesystemNode (in case an absolute
+	// path was passed). But we only use this to filter out directories.
 	FilesystemNode file(filename);
-	return (file.isValid() && !file.isDirectory());
+	if (file.isValid() && file.isDirectory())
+		return false;
+
+	// Next, try to locate the file by *opening* it in read mode. This has
+	// multiple effects:
+	// 1) It takes _filesMap and _defaultDirectories into consideration -> good
+	// 2) It returns true if and only if File::open is possible on the file -> good
+	// 3) If this method is misused, it could lead to an fopen call on a directory
+	//    -> bad!
+	// 4) It also checks whether we can read the file. This is not 100%
+	//    desirable; after all, even when we can't read it, the file is present.
+	//    Since this method is often used to check whether a file should be
+	//    re-created, that's not nice.
+	//
+	// TODO/FIXME: We should clarify the semantics of this method, and then
+	// maybe should introduce several new methods:
+	//   fileExistsAndReadable
+	//   fileExists
+	//   fileExistsAtPath
+	//   dirExists
+	//   dirExistsAtPath
+	// or maybe only 1-2 methods which take some params :-).
+	
+	File tmp;
+	return tmp.open(filename, kFileReadMode);
 }
 
 void File::close() {
-- 
cgit v1.2.3