> Do you have a list of the methods?
>
Yes.
https://drive.google.com/file/d/0BzwRg-R9g_6tY3dfYjBfQUppMzhIRnpXRWNzU0JQa1ZlUHZV/view?usp=sharing
and
https://drive.google.com/file/d/0BzwRg-R9g_6tRG56OFk0SmxLS3pucVRKTjd6ckpXNm1kUmFJ/view?usp=sharing
I was surprised hearing POSIX 1003-2013 has ~1300 fun
On Dec 26, 2016 1:28 PM, "Saeed Ehteshamifar" wrote:
On Thu, Dec 22, 2016 at 12:28 AM, Joel Sherrill wrote:
>
>
> On Tue, Dec 20, 2016 at 2:53 PM, Gedare Bloom wrote:
>
>> Option #1 writing a script is better. We occasionally add
>> implementations for POSIX features as needed for various co
On Thu, Dec 22, 2016 at 12:28 AM, Joel Sherrill wrote:
>
>
> On Tue, Dec 20, 2016 at 2:53 PM, Gedare Bloom wrote:
>
>> Option #1 writing a script is better. We occasionally add
>> implementations for POSIX features as needed for various compliance
>> test requirements or application portability.
On Tue, Dec 20, 2016 at 2:53 PM, Gedare Bloom wrote:
> Option #1 writing a script is better. We occasionally add
> implementations for POSIX features as needed for various compliance
> test requirements or application portability.
>
>
POSIX compliance is desirable within the limits of a single pr
Option #1 writing a script is better. We occasionally add
implementations for POSIX features as needed for various compliance
test requirements or application portability.
On Thu, Dec 15, 2016 at 9:29 AM, Saeed Ehteshamifar
wrote:
> Hello,
>
> For Slingshot, an RTEMS-targeted fault-injection tool
Hello,
For Slingshot, an RTEMS-targeted fault-injection tool for the POSIX API, I
need to remove the tests that correspond to unimplemented/unimplementable
POSIX functions/constants/etc. I can either
1. write a script that searches for "Unimplemented" and "Unimplementable"
in the doc's source, and
