That's the idea of hints. Telling you you need to look at the code once,
and if it's ok => good. But if the hint was correct => fix it.
But if you later change your code it may become not ok again. I don't think
that this is good working practice. I would prefer to have the compiler
recognize
Vinzent Höfler wrote:
Rainer Stratmann :
Am Thursday 19 November 2009 23:16:26 schrieb Vinzent Höfler:
{$HINTS OFF}
... code ...
{$HINTS DEFAULT}
maybe? Whereas DEFAULT restores the switch to the original state.
But then you have to do it everywhere in the code instead of on
Rainer Stratmann :
> Am Thursday 19 November 2009 23:16:26 schrieb Vinzent Höfler:
> >
> > {$HINTS OFF}
> >
> > ... code ...
> >
> > {$HINTS DEFAULT}
> >
> > maybe? Whereas DEFAULT restores the switch to the original state.
>
> But then you have to do it everywhere in the code instead of one time
Rainer Stratmann wrote:
Am Thursday 19 November 2009 23:16:26 schrieb Vinzent Höfler:
Martin :
Ideally it would be, if there was a directive or similar, to suppress it
for given lines (or statements).
one that is easier than {$push} { $HINT OFF} ... {$POP}
{$HINTS OFF}
... code
Am Thursday 19 November 2009 23:16:26 schrieb Vinzent Höfler:
> Martin :
> > Ideally it would be, if there was a directive or similar, to suppress it
> > for given lines (or statements).
> > one that is easier than {$push} { $HINT OFF} ... {$POP}
>
> {$HINTS OFF}
>
> ... code ...
>
> {$HINTS DEFAUL
Martin :
> Ideally it would be, if there was a directive or similar, to suppress it
> for given lines (or statements).
> one that is easier than {$push} { $HINT OFF} ... {$POP}
{$HINTS OFF}
... code ...
{$HINTS DEFAULT}
maybe? Whereas DEFAULT restores the switch to the original state.
Vinze
Jonas Maebe wrote:
On 19 Nov 2009, at 22:50, Rainer Stratmann wrote:
Yes, but for that is the compiler-switch $PASS_VAR_NO_HINT ON.
Then no hint is put out by the compiler.
When using FPC 2.4.0rc1 or later:
a) compile your code with -vq
b) note the message number for the warning/note/h
