ino_t type definition

[Victor V. Vengerov]

Hi,

Joel Sherrill wrote:

>
>
> > => Cygwin uses unsigned long.
> >
> > But this code also means that you can't rely on any implicit assumptions
> > on ino_t's size if your code is supposed to be portable.
>
> That statement applies to all types defined by C Standard Libraries and POSIX.
> You can't depend on anything size-wise.

IMHO, that statement applies to application code: application code should not
depend on such limits. Eugene means that file system implementation inside
RTEMS may require more than 16 bit i-node. File system is not an
application-level
code. I think, file system code (which is part of specific POSIX system
implementation)
may use some assumptions about ino_t width.

Are you agree with us that ino_t should be made wider?

Regards,
Victor



--
Victor V. Vengerov
OKTET Ltd.
Phone: office +7 812 4284384, home +7 812 4281653, mobile +7 812 9389372
Ulianovskaya st., 1, St.-Petersburg 198504, Russia


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20011111/afcf4f62/attachment-0001.html>