compile time warnings on solaris, modwsgi-3.1

[GoogleCodeExporter]

"mod_wsgi.c", line 10451: warning: statement not reached
"mod_wsgi.c", line 10533: warning: statement not reached

Original issue reported on code.google.com by rupert.t...@gmail.com on 15 Dec 2009 at 4:48

[GoogleCodeExporter]

And the compiler is technically correct.

In both cases it relates to activity of thread where the thread never actually 
exits. As such, there is a 'while (1)' loop 
encompassing what the thread does. The threads would only exit by virtue of 
process being destroyed.

One could possible create a dummy variable which is set to be true and have 
while() loop refer to that, but probably 
not worth the trouble and then other compilers may complain that variable isn't 
ever being set exception for point of 
initialisation.

There are much worse compiler warnings than this if one uses -Wall option with 
gcc. Haven't got round to cleaning 
them up yet.

I'll leave this open for now to remind me to address all -Wall warnings, but 
ultimately none of it affects operation of 
code.

Original comment by Graham.Dumpleton@gmail.com on 16 Dec 2009 at 12:01

• Changed state: Accepted
• Added labels: Type-Other
• Removed labels: Type-Defect

[GoogleCodeExporter]

Haven't done anything about the statement not reached errors, but have got rid 
of other -Wall errors in revision 
1557.

Original comment by Graham.Dumpleton@gmail.com on 1 Apr 2010 at 4:37

• Changed state: WontFix