econjack:
I disagree. The purpose of setup() is to establish the operation environment for the program. If you stay with the intended use of setup(), there is no reason to call it a second time. If you want to play games with setup() and use it for something beyond, or instead of, what it's intended for, that's your prerogative. However, I do not think that calling it a second time, if it's already accomplished its intended purpose, is good coding practice. Indeed, I don't think I've ever seen someone explicitly call setup().
There's a big difference between "I believe its bad form", which is what you're saying now, and "you should never call it", which is what you said earlier. Functionally, there is no reason you can't, or even shouldn't, do it. And I can imagine circumstances where it might be a reasonable thing to do, whether it fits your concept of good style or not.
Regards,
Ray L.