Hi!
I just wondered if the file-related primitives shouldn't raise the I/O
conditions from (rnrs io ports) instead of just using `raise/strerror'.
For example:
> (file-readable? "/does/not/exist")
Condition trapped by debugger.
Condition components:
1. &error
2. &who: file-readable?
3. &message: "ENOENT: No such file or directory"
4. &i/o-filename: "/does/not/exist"
I'd like to see something like that instead:
Condition components:
1. &error
2. &who: file-readable?
3. &message: "ENOENT: No such file or directory"
4. &i/o-file-does-not-exist: "/does/not/exist"
Would that be a reasonable change? If so, I could try to come up with a
patch.
[ BTW, I thought I'd use the opportunity to plug two bugs reported by me
which (a) have a patch and (b) should be quite uncontroversial:
- Make libffi auto-detected by configure
https://bugs.launchpad.net/ikarus/+bug/288748
- put-string doesn't allow optional start/count args
https://bugs.launchpad.net/ikarus/+bug/333044
]
Regards, Rotty
