Tim Ringenbach spake unto us the following wisdom:
> Richard Laager wrote:
> >Feel free to create
> >a patch to fix these warnings and submit it to the patch tracker at
> Actually I thought those kinds of warnings were related to your version=
> of tcl, and were unavoidable (either we'd have them for 1 version, or=20
> the other). Ethan can correct me if I'm misremembering.
This is correct. It's a difference in const definitions between 8.3
and 8.4, if I remember correctly. I believe there is supposed to be a
way to Fix it Right based on their defined TCL_CONST stuffs, but I
couldn't figure it out in a brief look, and then someone went and
committed a patch that just changed it so that the *other* version
complained, and that made people happy. I guess the complaining
version is falling out of favor anyway, or something.
I should like to point out, because we seem to have some sort of
warning fetish, that warnings are not *necessarily* a problem, and
silencing warnings just by making them shut up is not always a good
thing ... if a warning indicates an actual possible bug, you shouldn't
just go in and make it shut up; likewise, if a warning is due to the
construction of a library and is difficult to silence, you shouldn't
necessarily just make it shut up (in this case, because it was more of
a pushing the warnings around than a shutting up). Warnings are a
tool, and knowing when and how to use them is valuable...
The laws that forbid the carrying of arms are laws [that have no remedy
for evils]. They disarm only those who are neither inclined nor
determined to commit crimes.
-- Cesare Beccaria, "On Crimes and Punishments", 1764