Re: macro warning persists even after deleting all macros
This happens because the module that held the now-deleted code still
exists. Delete the module to avoid the warning.
.
Relevant Pages
- subroutine redefined warning
... How to avoid "subroutine redefined" warning in perl. ... Prev by Date: ...
(comp.lang.perl.misc) - Re: Watford Electronics
... > Take this as a warning as I have and avoid them. ... seems they just took Tiny's assets... ... Prev by Date: ...
(uk.comp.vendors) - Re: Watford Electronics
... >> Take this as a warning as I have and avoid them. ... > seems they just took Tiny's assets... ... Prev by Date: ...
(uk.comp.vendors) - Re: Watford Electronics
... > Take this as a warning as I have and avoid them. ... out of curiosity, who do you use these days, as it seems to me you've warned ... Prev by Date: ...
(uk.comp.vendors) - Re: dereferencing type-punned pointer will break strict-aliasing rules
... our warning flags are missing other new gcc warnings. ... object code size (the memcpy gets optimized away in almost the same way ... The temporary variable with a basic type is to avoid gcc getting confused ... There is no problem loading the source operand since only its address ...
(freebsd-current) |
|
