Hallo Joel,
I am in favour of RTEMS_INTERRUPTED and not RTEMS_EINTER since
abbreviations are not used in the Classic API in general.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail
o_read(). The issue is that we
> don't have
> > anything that maps to EINTR in the rtems_status_code enumeration.
> >
> > Is there any objection to adding RTEMS_INTERRUPTED as a status code?
> >
> > I am open to suggestions for a better name.
> >
>
>
s_code enumeration.
>
> Is there any objection to adding RTEMS_INTERRUPTED as a status code?
>
> I am open to suggestions for a better name.
>
Do you see a use for RTEMS_INTERRUPTED instead of to support EINTR defined
behavior? If you don't I'd name it RTEMS_EINTR so tha
/EINTR but it
returns -1/errno
based on rtems_status_code from rtems_io_read(). The issue is that we don't
have
anything that maps to EINTR in the rtems_status_code enumeration.
Is there any objection to adding RTEMS_INTERRUPTED as a status code?
I am open to suggestions for a better name.
T
