Re: [Chicken-hackers] [PATCH] proposed bugfix for #706

[Christian Kellermann]

* felix winkelmann <address@hidden> [110929 12:15]:
> >> > 
> >> > I am not quite sure I understand this correctly. Catch the error
> >> > and if it is an overflow, redo it with a flonum? I am not sure if
> >> > this is even possible since the internal check is against whether
> >> > you are a 32-bit application and your off_t datatype is large enough
> >> > to hold the size.
> > 
> > I see. I haven't found a different way of getting a filesize in my
> > Stephens yet.
> > 
> 
> Well, then we can just set the size slot to #f and have to check
> on the Scheme side, when the size is accessed (and throw an error
> in that case).

Ok, we can signal the error this way. We should also investigate
the compatibility of this -D_FILE_OFFSET_BITS=64 stuff.

> >> What other errors do you mean specifically?
> > 
> > EACCES EBADF EFAULT ELOOP ENAMETOOLONG ENOMEM EOVERFLOW
> > 
> 
> The easiest would probably be to return something indicating
> an error. Better would be to add an additional error code in
> barf (a generic "file access error", perhaps?) and call that
> in C_file_info_2.

Yes, I have already proposed this. Just not in C_file_info_2 yet.

Kind regards,

Christian

-- 
Who can (make) the muddy water (clear)? Let it be still, and it will
gradually become clear. Who can secure the condition of rest? Let
movement go on, and the condition of rest will gradually arise.
 -- Lao Tse.