FillByte(oSearchOptions, SizeOf(oSearchOptions), 0);
oSearchOptions := []; //It's an empty set
Bart
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Thanks Bart, forget my silly comments before, you did it cleverly.
- Original Message
From: Bart bartjun...@gmail.com
To: FPC-Pascal users discussions fpc-pascal@lists.freepascal.org
Sent: Thu, April 15, 2010 10:02:33 PM
Subject: Re: [fpc-pascal] Initializing a record-type variable to
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
Thank you very much Jose, that's a detail explanation. Forget my wrong
observation before.
- Original Message
From: José Mejuto joshy...@gmail.com
To: FPC-Pascal users discussions fpc-pascal@lists.freepascal.org
Sent: Thu, April 15, 2010 10:11:03 PM
Subject: Re[2]: [fpc-pascal]
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
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?
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?
- Original Message
From: José Mejuto joshy...@gmail.com
