Document Number: AUSTIN/17r1

Title: Options Margin Markers

Revision Date: 1999-03-04
Original Date: 1999-03-02

Source: Andrew Josey, Chair

Action: for review 


Options handling in POSIX is used by many "If {OPTION} then ....".
Its proposed to use the margin notation and shaded text for 
many options - the rationale being that this leads to cleaner,
simpler easier to understand text for the application writer.
This means we need to map the POSIX options to margin codes.
(note a separate task is to consider whether to remove some
options)

Attached is a list of options together with Margin Markers

Options we can discuss:

POSIX 1003.1

This first group is required by FIPS supporting systems.
Its recommended that these become mandatory.
		{_POSIX_JOB_CONTROL}  	
		{_POSIX_VDISABLE}
		{_POSIX_SAVED_IDS}


We need margin markers for these:

		{_POSIX_ASYNCHRONOUS_IO}    AIO
		{_POSIX_FSYNC}		    FSC
		{_POSIX_MAPPED_FILES}	    MF
		{_POSIX_MEMLOCK}	    ML
		{_POSIX_MEMLOCK_RANGE}	    MLR
		{_POSIX_MEMORY_PROTECTION}  MPR
		{_POSIX_MESSAGE_PASSING}    MSG
		{_POSIX_PRIORITIZED_IO}     PIO
		{_POSIX_PRIORITY_SCHEDULING} PIO
		{_POSIX_REALTIME_SIGNALS}    RTS
		{_POSIX_SEMAPHORES}	     SEM
		{_POSIX_SHARED_MEMORY_OBJECTS} SHM
		{_POSIX_SYNCHRONIZED_IO}     SIO
		{_POSIX_TIMERS}		     TMR

		{_POSIX_THREADS}		THR

		{_POSIX_THREAD_SAFE_FUNCTIONS}  TSF
		{_POSIX_THREAD_ATTR_STACKADDR}	TSA
		{_POSIX_THREAD_ATTR_STACKSIZE}  TSS
		{_POSIX_THREAD_PROCESS_SHARED}  TSH

		{_POSIX_THREAD_PRIO_INHERIT}    TPI
		{_POSIX_THREAD_PRIORITY_SCHEDULING}  TPS
		{_POSIX_THREAD_PRIO_PROTECT}	TPP

		_POSIX_RAW_SOCKETS RS
		_POSIX_XTI XTI
		_POSIX_IPV6 IP6
		_POSIX_IPV6_EXT IPE ?? (probably not)