physfs.h
changeset 137 66bddb94b6e0
parent 132 b53fa5093749
child 147 5e1eda65ceb3
--- a/physfs.h	Mon Mar 25 05:01:29 2002 +0000
+++ b/physfs.h	Mon Mar 25 05:02:12 2002 +0000
@@ -596,6 +596,9 @@
  *
  * A directory must be empty before this call can delete it.
  *
+ * Deleting a symlink will remove the link, not what it points to, regardless
+ *  of whether you "permitSymLinks" or not.
+ *
  * So if you've got the write dir set to "C:\mygame\writedir" and call
  *  PHYSFS_delete("downloads/maps/level1.map") then the file
  *  "C:\mygame\writedir\downloads\maps\level1.map" is removed from the
@@ -606,6 +609,10 @@
  *  actual file won't be removed until all processes that have an open
  *  filehandle to it (including your program) close their handles.
  *
+ * Chances are, the bits that make up the file still exist, they are just
+ *  made available to be written over at a later point. Don't consider this
+ *  a security method or anything.  :)
+ *
  *   @param filename Filename to delete.
  *  @return nonzero on success, zero on error. Specifics of the error can be
  *          gleaned from PHYSFS_getLastError().