| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
<sys-stat> class (See section 6.21.3.4 File stats).
If the named path doesn't exist, #f is returned.
If path is a symbolic link, these functions queries the attributes of the file pointed by the link, unless an optional argument follow-link? is given and false.
MzScheme and Chicken have file-size. Chicken also has
file-modification-time, which is file-mtime.
#t if path exists and readable/writable/executable
by the current effective user, respectively.
This API is taken from STk.
file-eq? and file-eqv? checks if path1 and path2
refers to the identical file, that is, whether they are on the same
device and have the identical inode number. The only difference is
when the last component of path1 and/or path2 is a symbolic
link, file-eq? doesn't resolve the link (so compares the links
themselves) while file-eqv? resolves the link and compares the
files referred by the link(s).
file-equal? compares path1 and path2 considering their
content, that is, when two are not the identical file in the sense of
file-eqv?, file-equal? compares their content and returns
#t if all the bytes match.
The behavior of file-equal? is undefined
when path1 and path2 are both directories.
Later, it may be extended to scan the directory contents.
<sys-stat> object (See section 6.21.3.4 File stats).
The mtime is taken from the stat structure.
<time> object. The time is used as the mtime.
;; compare "foo.c" is newer than "foo.o" (file-mtime>? "foo.c" "foo.o") ;; see if "foo.log" is updated within last 24 hours (file-mtime>? "foo.c" (- (sys-time) 86400)) |
file-mtime=?, except these checks file's change time
and access time, respectively.
All the variants of <, <=, >, >= are also
defined.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |