Liste des Groupes | Revenir à cl c |
On 28/11/2024 22:38, Keith Thompson wrote:Bart <bc@freeuk.com> writes:>On 28/11/2024 19:58, Keith Thompson wrote:You say T is an alias (what, a macro?) for 'const int', you show codeBart <bc@freeuk.com> writes:>
[...]I think 'const' is confusing for similar reasons that VLAs can be bothSure. For example, given
confusing and awkward to implement.
>
That's because both really apply to /types/, not directly to variables.
const int n = 42;
n is of type `const int`, and &n is of type `consts int*`. Of course
that implies that n itself is const.
But that is a separate thing. Suppose T was an alias for 'const int'. Then:
>
T x; // defines a readonly variable (which probably needs
// initialising)
T* y; // defines a variable pointer
>
'const' is out of the picture.
using T, and then you say "'const' is out of the picture". If you
have a point, it escapes me.
Well, can you see 'const' in my example? You can't tell x is readonly
by only looking at this.
Yes, and you seem determines to make it easier to get mixed up.>
C doesn't require any help from me for confusing features.
The OP said
it was confusing and I tried to point out why it might be.
>
Obviously you as C expert will never be confused. But there are lots
of less expert users of the language.
Les messages affichés proviennent d'usenet.