warn 5024

[Чебурашка]

Hello,
I work under lazarus-linux (see below the version). For some reason I have a unit that generates several hints about unsed params (this is a tempoarary situation, eventually I will fix their usage).

When I use Lazarus to buid, I see in the messages window "Hide message by adding {$warn 5024 off} to <MyUnit.pas>".
If I click this menu item, the line is added at top.

Code: Pascal  [Select][+][-]

1. unit MyUnit;
2.  
3. {$WARN 5024 off : Parameter "$1" not used}
4.  
5. interface
6.  

but when rebuilding I still see all the messages that were supposed to be hidden.


Is that about my Lazarus version or am I doing smtg wrong?

[qk]

Have you tried with simple line below?

Code: Pascal  [Select][+][-]

1. {$WARN 05024 OFF}

[Thaddy]

Have you tried with simple line below?

Code: Pascal  [Select][+][-]

1. {$WARN 05024 OFF}

That is wrong, since it is not 05024, but 5024. (Yes that means a different thing!)
It is also wrong because with {$WARN number ON/OFF everything after ON/OFF up until the closing bracket is interpreted as a comment and perfectly legal.

In principle the original line is therefor correct and that unit should not return parameter not used warnings, unless there is an overriding command line option used.
We need to know the build settings if that unit still throws that warning, but note that the uses clause from that unit can also pull in other units that may reset the value ON/OFF...
I would rather see the whole unit if it is possible.
Another note is that you can use {$PUSH}/{$POP} around the offending declarations:

Code: Pascal  [Select][+][-]

1. {$push}{$warn 5024 off}
2. procedure test(par:integer);
3. begin
4. //
5. end;
6. {$POP}

which can help to remove the warning only when it is really needed.

[PascalDragon]

Have you tried with simple line below?

Code: Pascal  [Select][+][-]

1. {$WARN 05024 OFF}

That is wrong, since it is not 05024, but 5024. (Yes that means a different thing!)

They are the same. Pascal uses & for octal numbers, not 0.

but when rebuilding I still see all the messages that were supposed to be hidden.

Do you have a more complete example than just a snippet?

[Thaddy]

In this case I am right, because the compiler, well the parser threats as string, so 05024 <> 5024 by definition.

[bytebites]

Result is same with 5024 and 05024.

[Thaddy]

No it is not! the interpreter part evaluates as string, not as a numeric value... So they are very different.

[bytebites]

Try it yourself.

Code: Pascal  [Select][+][-]

1. program Project1;
2.  
3. {$WARN 05024 OFF}
4.  
5. procedure foo(unused:boolean);
6. begin
7.   writeln('hello');
8. end;
9.  
10. begin
11.   foo(false);
12. end.
13.  

[PascalDragon]

In this case I am right, because the compiler, well the parser threats as string, so 05024 <> 5024 by definition.

You are wrong. Any digit in the range of '0'..'9' after a whitespace or non-identifier character will lead to the parsing of a number and not a string (see tscannerfile.readtoken in scanner.pas at around line 5249). A string constant can only be started by a '.

[WooBean]

A string constant can only be started by a '.

Not all in PascalDragon's post is true in context of the subject. Directive $WARN (FPC 3.2.2) has about 20 predefined identifiers (CONSTRUCTING_ABSTRACT, ... ,INTF_RAISE_VISIBILITY) which can be used to switch on/off compiler warnings. Using those identifiers as strings (e.g. {$WARN 'NO_RETVAL' OFF}) will not work.

[PascalDragon]

A string constant can only be started by a '.

Not all in PascalDragon's post is true in context of the subject. Directive $WARN (FPC 3.2.2) has about 20 predefined identifiers (CONSTRUCTING_ABSTRACT, ... ,INTF_RAISE_VISIBILITY) which can be used to switch on/off compiler warnings. Using those identifiers as strings (e.g. {$WARN 'NO_RETVAL' OFF}) will not work.

I never said that you can use string constants with {$warn}, I only said that string constants are started with ' (and that's what this was about: string constants). CONSTRUCTING_ABSTRACT and Co. are exactly what you mentioned: identifiers. That's a difference.