Paul Ishenin schrieb:
> Graeme Geldenhuys wrote:
>
>> As I stated in the other mailing list. It's not about a obsession to get
>> hint & warning free code. It's about spoting REAL issues in code between
>> all the crap the compiler currently spits out. If your project uses a
>> lot of structure types, you can quickly sit with thousands of lines of
>> compiler hints like this one. There is no easy way of spotting real hint
>> compared to fake (useless) hints. And I definitely don't have the time
>> to seek through my rather large (200k + LOC projects) projects hint
>> output to try and figure out what is real and what is useless hints.
>
> Then maybe the solution is to add someting like
>
> {$uninitialized_arguments_check_for_functions off}
> procedure FillChar(var ...)
> begin
> ...
> end;
> {$uninitialized_arguments_check_for_functions on}
>
> Compiler will add a flag for each var/const argument that they dont
> require that checks.
This looks really ugly :) Maybe a better solution is to implement a
compiler internal counter part to finalize which simply zeros the
variable and where the compiler knows that the variable must not be
initialized before.
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
