I still need compiler hint generated by FPC at compiling (I don't want to turn it off), but the hint sometime disturbs me because it's a false-postive detection.

Supposing I have a record-type variable, could someone here tell me how to initialize it properly so that FPC could notice the initialization, since the FillByte() and FillChar() way do not cause FPC aware of it?

This is part of my code:

var
  oSearchOptions: TSearchFileOptions;
FillByte(oSearchOptions, SizeOf(oSearchOptions), 0);

I got this compiler hint when compiling:
Variable "oSearchOptions" does not seem to be initialized.

Thanks for any comments.

Hello FPC-Pascal,

Wednesday, April 14, 2010, 5:13:51 PM, you wrote:

BA> Supposing I have a record-type variable, could someone here BA> tell me how to initialize it properly so that FPC could notice the BA> initialization, since the FillByte() and FillChar() way do not BA> cause FPC aware of it?

I'm using:

procedure InitRecord(out Rec; const ASize: SizeUint);
begin
{$PUSH}
{$HINTS OFF}
  FillByte(Rec,ASize,0);
{$POP}
end;

Unfortunatly it can not be inlined :( due the formal parameter.

Thanks for your reply José, but what is the philosophy behind the solution? and What are the reasons for $PUSH and $POP? Also, I tried to remove the $HINTS directive, and it worked fine without it. Could you explain this?

FillByte(oSearchOptions, SizeOf(oSearchOptions), 0);

oSearchOptions := []; //It's an empty set

Bart

Thanks Bart, forget my silly comments before, you did it cleverly.

Hello FPC-Pascal,

Thursday, April 15, 2010, 6:43:41 AM, you wrote:

BA> Thanks for your reply José, but what is the philosophy behind BA> the solution? and What are the reasons for $PUSH and $POP? Also, I BA> tried to remove the $HINTS directive, and it worked fine without BA> it. Could you explain this?

Rec parameter is qualified as "out" so, the enter values is non-important and the compiler will not generate the "non initialized" hint.

The $PUSH pushes in fpc stack the current settings about hints, warnings, alignement, etc, then I change the hints to off, because FillByte could produce (not sure with formal parameter) the hint message and then $POP restores previous settings about hints and other directives.

Thank you very much Jose, that's a detail explanation. Forget my wrong observation before.