[Cfp-interest 3315] Re: C26 Complex Related Changes

[Jim Thomas]

Here is a suggestion for separating C26-cmplx-mods-aug24-body-67 into three topics, each for further investigation and wording for specific changes:

1. complex.h Introduction 7.3.1
Incorrect application of N3274
Problematic definition of _Complex_I
Mistaken specification in #4

2. cproj 7.3.9.5 
Problematic reference to complex infinities
Incorrect reference to "Riemann sphere"

3. Miscellaneous editorial suggestions

- Jim Thomas


> On Sep 16, 2024, at 9:09 AM, Jim Thomas <jaswthomas at sbcglobal.net> wrote:
> 
> Here’s a CFP wiki link to the file:
> 
> https://wiki.edg.com/pub/CFP/WebHome/C26-cmplx-mods-aug24-body-67-jwt.pdf
> 
> - Jim Thomas
> 
>> On Sep 15, 2024, at 9:54 PM, Jim Thomas <jaswthomas at sbcglobal.net> wrote:
>> 
>> Here is a file with inline comments for the first of the four papers (C26-cmplx-mods-aug24-body-67):
>> 
>> <C26-cmplx-mods-aug24-body-67-jwt.pdf>
>> 
>> - Jim Thomas
>> 
>>> On Aug 25, 2024, at 5:08 AM, Damian McGuckin <damianm at esi.com.au> wrote:
>>> 
>>> 
>>> Hi all,
>>> 
>>> I have uploaded my suggestions.  Please provide feedback before the next meeting because there is way too much to cover during a single meeting. At the start, I explain in a block before the actual changes the rationale for some of the proposals. And then for each change, I briefly note why that change has been proposed.  To make it readable, I provide the entire paragraph because most changes are more than one or two words or phrases. I do not use a 'diff' except in one case because it is so trivial.
>>> 
>>> I think all are editorial although in one case the word complex is missing so that the existing text says a parameter has a type of 'float' when it meant 'float complex' which seems like extremely editorial.  Most of the changes are for consistency, that is, if words are used one way in one place, and then in related section later, a different wording style is used, I try and use the style which reads the best.
>>> 
>>> The domains for all special cases are now inequalities.
>>> 
>>> Let me know if you have a problem with these links.
>>> 
>>> There are a small number of changes to 6/Language and 7/Library.
>>> 
>>> 	https://wiki.edg.com/pub/CFP/WebHome/C26-cmplx-mods-aug24-body-67.pdf
>>> 
>>> The major consistency changes in the effective Introductions to Annex F
>>> and Annex G, i.e. F.10.1 and G.4.1 Introduction a Annex F (some of which
>>> are just an exercise in reordering), and improved explanations are:
>>> 
>>> 	https://wiki.edg.com/pub/CFP/WebHome/C26-cmplx-mods-aug24-annex-fg-intro.pdf
>>> 
>>> Note that there is one clause, G.2, that could move to the end of 7.3.1..
>>> 
>>> The special cases in Annex F and Annex G now have a consistent syntax.
>>> I distilled the most consistent existing syntax used for the special
>>> cases and then applied that rigorously (although I did moved the words
>>> about exceptions raised for each case to the end of the sentence).
>>> 
>>> The changes for consistency in Annex F are in:
>>> 
>>> 	https://wiki.edg.com/pub/CFP/WebHome/C26-cmplx-mods-aug24-annex-f.pdf
>>> 
>>> The changes for consistency in Annex G are in:
>>> 
>>> 	https://wiki.edg.com/pub/CFP/WebHome/C26-cmplx-mods-aug24-annex-g.pdf
>>> 
>>> Thanks - Damian
>>> _______________________________________________
>>> Cfp-interest mailing list
>>> Cfp-interest at oakapple.net
>>> http://mailman.oakapple.net/mailman/listinfo/cfp-interest
>> 
> 
> _______________________________________________
> Cfp-interest mailing list
> Cfp-interest at oakapple.net
> http://mailman.oakapple.net/mailman/listinfo/cfp-interest

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.oakapple.net/pipermail/cfp-interest/attachments/20241014/11d2f64d/attachment.htm>