Date: Mon, 12 Jun 2023 15:36:31 +0100
From: "Geoff Clare via austin-group-l at The Open Group"
<austin-group-l@opengroup.org>
Message-ID: <ZIctbxbRJcgJHpAG@localhost>
| Yes, I assumed some context rather than stating it. I should have
| said "In particular, when a signal is generated it can become pending
| for reasons other than being blocked".
That's no better, particularly in light of your explanation of what
"pending" means in the standard (which I was too lazy to go and check).
Signals never become pending because they're blocked, nor do they become
pending upon being unblocked.
| I'll edit the note to make that change.
Please make a somewhat different change, which just makes it clear that
some other signal may have become pending while this function is running,
and omit mentions of being blocked, which seem to be confusing things.
That, or don't add the application usage text at all. Maybe something
like "An unrelated signal may have become pending while..."
kre
