[Chicken-janitors] #707: ##sys#file-info needs to signal an error if the fstat syscall goes bad

[Chicken Trac]

#707: ##sys#file-info needs to signal an error if the fstat syscall goes bad
----------------------------+-----------------------------------------------
 Reporter:  ckeen           |       Owner:       
     Type:  defect          |      Status:  new  
 Priority:  major           |   Milestone:  4.8.0
Component:  core libraries  |     Version:  4.7.x
 Keywords:                  |  
----------------------------+-----------------------------------------------
 I think it is bad style to ignore the errno error signalling mechanism
 when doing syscalls. Bug #706 shows that this can result in serious
 mischief.

 ##sys#file-info is the first culprit that I have identified, but I suspect
 all runtime calls lack a error propagation mechanism.

 Maybe a more general approach on how to do this is needed.
 At the time of writing this I am favoring raising exn i/o conditions for
 the exceptional cases. Also would these calls be reentrant?

-- 
Ticket URL: <http://bugs.call-cc.org/ticket/707>
Chicken Scheme <http://www.call-with-current-continuation.org/>
Chicken Scheme is a compiler for the Scheme programming language.