diff options
author | Jim Blandy <jimb@red-bean.com> | 1996-12-18 21:42:09 +0000 |
---|---|---|
committer | Jim Blandy <jimb@red-bean.com> | 1996-12-18 21:42:09 +0000 |
commit | 4dc2435aef1e447fe0cf370edb1db7d9f37fe385 (patch) | |
tree | 0122d9ce268c1885b84898cbcee4713e7659ccf5 /libguile/root.c | |
parent | 35de7ebe4a2f424a49bdcc856baaa0d61b978809 (diff) | |
download | guile-4dc2435aef1e447fe0cf370edb1db7d9f37fe385.tar.gz |
In some cases, the code is fine, but GCC isn't smart enough to
figure that out; this usually happens when one variable is only
initialized and used when a particular condition holds true, and
we know that condition will never change within a given invocation
of the function. In this case, we simply initialize the variables
to placate the compiler, hopefully to a value which will cause a
crash if it is ever actually used.
* print.c (scm_iprin1): Initialize mw_pos.
* read.c (scm_lreadrecparen): Initialize tl2, ans2.
* throw.c (scm_ithrow): Initialize dynpair.
* unif.c (scm_uniform_vector_ref): Initialize cra.
* struct.c (init_struct): Initialize prot.
* mbstrings.c (scm_print_mb_symbol): Initialize mw_pos and inc.
Diffstat (limited to 'libguile/root.c')
0 files changed, 0 insertions, 0 deletions