-
-
Notifications
You must be signed in to change notification settings - Fork 33.9k
gh-143674: document complex representation using f/d formats in struct #143879
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -2696,7 +2696,9 @@ these can be preceded by a decimal repeat count:\n\ | |
| x: pad byte (no data); c:char; b:signed byte; B:unsigned byte;\n\ | ||
| ?: _Bool (requires C99; if not available, char is used instead)\n\ | ||
| h:short; H:unsigned short; i:int; I:unsigned int;\n\ | ||
| l:long; L:unsigned long; f:float; d:double; e:half-float.\n\ | ||
| l:long; L:unsigned long; f:float; d:double; e:half-float.\n\ | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. That change is unrelated.
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. yeah my bad, it is just whitespace error on my side |
||
| For complex numbers, the real and imaginary parts are represented by two\n\ | ||
| consecutive values of the specified floating-point type.\n\ | ||
|
Comment on lines
+2700
to
+2701
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. yeah my bad. this is my first PR and i am still getting accustomed to contributing to open source. i missed checking for an existing PR on the issue. ill make sure to do that in the future. thanks for the review. i am closing this PR now. |
||
| Special cases (preceding decimal count indicates length):\n\ | ||
| s:string (array of char); p: pascal string (with count byte).\n\ | ||
| Special cases (only available in native format):\n\ | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The are note (10) right below. Much more precise and clear, IMO. What means "may also be"?
Are you used LLM to generate PR? It looks you haven't read the documentation by yourself. Please see this:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i have read the documentation myself and have composed it myself only. how about this then?
"Complex numbers are represented (by convention), using two consecutive floating-point format characters. In this case, real part is stored first, and then the imaginary part. the format characters
fandddetermine the type used for each component"is this okay?