in reply to Re^3: Bad file descriptor when trying to close file handle
in thread Bad file descriptor when trying to close file handle
well kind of, printing to an unlinked file in ">>" mode seems to do nothing, but no error message either.
It might seem to you that it does nothing, but that's not the case. It does what I said it does: It writes to the file as it always does.
Open the file twice, once for reading and once for writing. Then delete the directory entry you used to open the file, then write to it, then read from it. You'll see it's there.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^5: Bad file descriptor when trying to close file handle
by ikegami (Patriarch) on Mar 03, 2022 at 15:27 UTC | |
|
Re^5: Bad file descriptor when trying to close file handle
by LanX (Saint) on Mar 03, 2022 at 15:25 UTC | |
by ikegami (Patriarch) on Mar 03, 2022 at 15:28 UTC | |
by LanX (Saint) on Mar 03, 2022 at 16:01 UTC | |
by ikegami (Patriarch) on Mar 03, 2022 at 16:05 UTC | |
by ikegami (Patriarch) on Mar 03, 2022 at 16:11 UTC | |
|