On 5/14/25 07:00, David Brown wrote:
...
My interpretation matches yours. I can't find any indication in the
standard of a definition of what an "array" actually means
This is a problem with all of the derived types (6.2.5p25). There are definitions of the terms "array type", "structure type:, "union type", "function type", and "pointer type", but no definitions of the things
that those types are types of. My interpretation is that for each of
those object types, "X" is short-hand for "an object of X type".
[...]
Tim Rentsch <tr.17687@z991.linuxsc.com> writes:
[...]
It isn't just that checking the condition cannot be done in general.
To be reliable the parameter length information would need to be
part of the function's type. That has implications for type
compatibility and also for the types of pointers-to-function. And
it would mean that removing a 'static' array length specification on
a function definition would necessitate also changing the functions
declarations, plus any affected pointers-to-function. Not worth it,
even if in theory it were doable.
[...]
In my opinion, keeping a function's definition and declarations
consistent is absolutely worth it, even if the language might not
require it.
Keith Thompson <Keith.S.Thompson+u@gmail.com> writes:[...]
Tim Rentsch <tr.17687@z991.linuxsc.com> writes:
In my opinion, keeping a function's definition and declarations
consistent is absolutely worth it, even if the language might not
require it.
Without some sort of accompanying rationale, this unadorned
statement of opinion conveys no useful information.
Keith Thompson <Keith.S.Thompson+u@gmail.com> writes:
Tim Rentsch <tr.17687@z991.linuxsc.com> writes:
In my opinion, keeping a function's definition and declarations
consistent is absolutely worth it, even if the language might not
require it.
Without some sort of accompanying rationale, this unadorned
statement of opinion conveys no useful information.
Tim Rentsch <tr.17687@z991.linuxsc.com> writes:
Keith Thompson <Keith.S.Thompson+u@gmail.com> writes:[...]
Tim Rentsch <tr.17687@z991.linuxsc.com> writes:
In my opinion, keeping a function's definition and declarations
consistent is absolutely worth it, even if the language might not
require it.
Without some sort of accompanying rationale, this unadorned
statement of opinion conveys no useful information.
I posted an opinion, clearly marked as my opinion. More than
eight months later, you felt the need to post a followup vaguely
expressing your opinion on my opinion.
On 28/01/2026 17:54, Tim Rentsch wrote:
Keith Thompson <Keith.S.Thompson+u@gmail.com> writes:
Tim Rentsch <tr.17687@z991.linuxsc.com> writes:
In my opinion, keeping a function's definition and declarations
consistent is absolutely worth it, even if the language might not
require it.
Without some sort of accompanying rationale, this unadorned
statement of opinion conveys no useful information.
That's an ironically appropriate use of "this". If you'd said "that"
it wouldn't have been true.
On Sat, 31 Jan 2026 03:53:09 +0000
Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk>
wrote:
On 28/01/2026 17:54, Tim Rentsch wrote:
Keith Thompson <Keith.S.Thompson+u@gmail.com> writes:
Tim Rentsch <tr.17687@z991.linuxsc.com> writes:
In my opinion, keeping a function's definition and declarations
consistent is absolutely worth it, even if the language might not
require it.
Without some sort of accompanying rationale, this unadorned
statement of opinion conveys no useful information.
That's an ironically appropriate use of "this". If you'd said "that"
it wouldn't have been true.
Care to elaborate for the benifit of non-native English readers?
Personally, in this particular context, I don't see how 'this' carries >different meaning from 'that'.
Michael S <already5chosen@yahoo.com> writes:
On Sat, 31 Jan 2026 03:53:09 +0000
Tristan Wibberley
<tristan.wibberley+netnews2@alumni.manchester.ac.uk> wrote:
On 28/01/2026 17:54, Tim Rentsch wrote:
Keith Thompson <Keith.S.Thompson+u@gmail.com> writes:
Tim Rentsch <tr.17687@z991.linuxsc.com> writes:
In my opinion, keeping a function's definition and declarations
consistent is absolutely worth it, even if the language might
not require it.
Without some sort of accompanying rationale, this unadorned
statement of opinion conveys no useful information.
That's an ironically appropriate use of "this". If you'd said
"that" it wouldn't have been true.
Care to elaborate for the benifit of non-native English readers? >Personally, in this particular context, I don't see how 'this'
carries different meaning from 'that'.
English is often ambiguous. 'This' in the context of Tim's
response is ambiguous and could be interpreted to refer to
Tim's response itself, rather than to Keith's statement.
| Sysop: | Jacob Catayoc |
|---|---|
| Location: | Pasay City, Metro Manila, Philippines |
| Users: | 5 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 24:10:20 |
| Calls: | 117 |
| Calls today: | 117 |
| Files: | 368 |
| D/L today: |
560 files (257M bytes) |
| Messages: | 70,913 |
| Posted today: | 26 |