The following program:

program Project1;
{$mode objfpc}{$H+}
var
   s:ansistring;
begin
   WriteLn('s <',s,'> always seems to be initialized to ''''');
end.

produces a Warning

Warning: Variable "s" does not seem to be initialized

Can this Warning be disabled for compiler-managed variables?

Howard

I recommend against it.

It can bite you in the leg, it has bitten me in the leg several times. For instance the result identifier for functions returning ansistring is particularly tricky.

Michael.

The point of the warning is that you did not assign a value to the variable, not necessarily that the contents are unknown. You get the same warning for global variables if you only use them in a main program. Removing unnecessarily assigning an empty string to such values would be a job for the compiler (which it currently does not yet do).

Jonas

I'm wondering if it's a question about global vs local variables warning: http://lists.freepascal.org/lists/fpc-devel/2012-November/030337.html

The warning is true for local vars and indeed it bites! (bites good when porting delphi to fpc), but should not be a problem for global vars (as in example above).

thanks,
Dmitry