Anton:
> So a file with a blank filename exists, does it?
> And if it exists, then I should be able to read it, right?
That's an odd little find. It seems to hover between being the current
directory, a bad file name, and the root directory name. Try these:
>> probe info? to-file ""
make object! [
size: 0
date: 8-Mar-2002/23:03:34
type: 'directory
]
;; so it's a directory (with creation info same as my current directory). But:
>> list-dir to-file ""
** Access Error: Cannot open /D/Rebol/
** Where: throw-on-error
** Near: list-dir to-file ""
;; no it isn't. But:
>> change-dir to-file ""
== %/D/Rebol/
;; Yes it is: it is my current/working directory after all. But:
>> list-dir dirize to-file ""
/a/ /c/ /d/ /e/ /f/ /g/ /h/ /z/
;; it is all my drives.
A case for feedback?
Sunanda.
--
To unsubscribe from this list, please send an email to
[EMAIL PROTECTED] with "unsubscribe" in the
subject, without the quotes.
