- changed status to resolved
File operation failure should raise &i/o instead of &assersion
Issue #202
resolved
Raising &asserion
is rather weird since it's executed. So must be &i/o
Comments (3)
-
reporter -
reporter - changed status to open
For Windows part
-
reporter - changed status to resolved
Interestingly, blind coding worked this time.
- Log in to comment
Rewriting file system APIs to return errno. This partially fixes
#202(on POSIX side)→ <<cset 7be09374eda8>>