Variable declarations in xcrypt.c

[Ben Lindstrom]

On Mon, 8 Sep 2003, Darren Tucker wrote:

> Hi All.
> 	I noticed that xcrypt.c now has some variable declarations after code
> within a block (for some sets of #ifdef's).  Won't that choke some
> compilers?  Should it do something like the attached?
>

Well.. the first #ifdef will never be triggered with the second set.  You
can't set shadowed and HAVE_GETPWANAM.  So it should be safe as it is.
However maybe it should be an #elif instead of a #endif #if ..

- Ben