«

Giuseppe wrote:

>>> Otherwise, use
>>> const Mystruct null_mystruct; /* will be initialized with nulls */

That statement should either be at file scope, or it should be
static const Mystruct null_mystruct;

This time I got it right, I think

> Mystruct da_azzerare;
>
> da_azzerare = null_mystruct;

That's fine.

> *( Mystruct *) &da_azzerare = *( Mystruct *) &null_struct;

Oh my gosh. You could, but don't. BTW, it should have been
*( const Mystruct *) &null_struct;
since you should not cast away const when you don't need to.

--
Hallvard

bd <> wrote:
> On Sun, 29 Jun 2003 15:28:00 +0000, Kevin Easton wrote:
>
>> Hallvard B Furuseth <h.b.furuseth(nospam)@usit.uio(nospam).no> wrote:
>>> Nils Emil P. Larsen wrote:
>>>
>>>> I have a pointer to a struct or an array of structs and I know the
>>>> lenght of the struct or array of structs.
>>>>
>>>> I need a elegant way to clear it with zeroes.
>>>>
>>>> Mystruct *mystruct; // Mystruct is a typedef
>>>
>>> If the struct contains nothing but integer (and character) elements,
>>> you can just do
>>> memset(mystruct, 0, array_length * sizeof(Mystruct))
>>> Otherwise, use
>>> const Mystruct null_mystruct; /* will be initialized with nulls */
>>
>> What basis do you have for that comment? Did you perhaps mean either:
>>
>> const Mystruct null_mystruct = { 0 };
>>
>> or
>>
>> static const Mystruct null_mystruct;
>>
>> ?
>
> That's implicit in static and file scope variables.

It was neither static nor file scope (because the next line was a
statement, which can't appear at file scope).

- Kevin.