Email List: Xaustin-group-lX
[All Lists]

Re: Minutes of the August 14th 2008 teleconference

To: austin-group-l@xxxxxxxxxxxxx
Subject: Re: Minutes of the August 14th 2008 teleconference
From: Geoff Clare <gwc@xxxxxxxxxxxxx>
Date: Wed, 27 Aug 2008 12:18:46 +0100
References: <1218787608.8714.2.camel@xxxxxx>
Andrew Josey <ajosey@xxxxxx> wrote, on 15 Aug 2008:
>
> Minutes of the 14 August 2008 Teleconference     Austin-438 Page 1 of 1
> Submitted by Andrew Josey, The Open Group.             August 15 , 2008

> XSH ERN 250 setlocale Accept as marked 
> 
> Send this down the interps track.
> The standard states the requirements for setlocale() , and
> conforming implementations must conform to this. However, concerns have
> been raised about this which are being referred to the sponsor.
> (Target for TC1)
> 
>  Change line 41265f to
> 
>    [...] The application shall not modify the string returned.  The
>    returned string pointer might be invalidated or the string content
>    overwritten by a subsequent call to setlocale().
> 
> 
> Add new para as last para of DESCRIPTION
> 
> The implementation shall behave as if no function defined
> in this volume of POSIX.1-200x calls set setlocale()

Delete "set" (so it ends "... calls setlocale()").

> A new para of APP USAGE
> 
> Applications that use multiple threads should use uselocale()
> in preference to setlocale().

This is too wide - it includes cases where setlocale() is okay, such
as setting the locale once near the beginning of main(), before creating
additional threads.  I suggest instead:

    "In order to make use of different locale settings while
    multiple threads are running, applications should use
    uselocale() in preference to setlocale()."

> XSHbug3 ERN 4 sigaction Accept as marked
> 
> Fix the application usage on sigaction() page 1919 so its consistent with
> the signal() page
> 
> Target for TC1
> (not interpretation necessary as informative text)

This aardvark spawned an email discussion in which a lot of problems
with the signal() page were identified.  In particular, I suggested
a change to the signal() page in austin-group-l 11621.

Either that change should be included in the resolution for XSHbug3
ERN 4, or if preferred I can submit a new aardvark against the
signal() page.  (If the latter, then XSHbug3 ERN 4 should make clear
that it needs to be applied _after_ the signal() page change.)

-- 
Geoff Clare <g.clare@xxxxxx>
The Open Group, Thames Tower, Station Road, Reading, RG1 1LX, England

<Prev in Thread] Current Thread [Next in Thread>