Bug 150215

Summary: missing return statement
Product: [Fedora] Fedora Reporter: David Binderman <dcb314>
Component: supertuxAssignee: Steven Pritchard <steve>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 3CC: steve
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-03-20 18:52:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description David Binderman 2005-03-03 19:54:31 UTC
Description of problem:

I just tried to compile supertux-0.1.2-1 from 
Redhat Fedora Extras development tree with the Intel C compiler.

The Intel compiler said

bitmask.cpp(81): warning #1011: missing return statement at end of
non-void function "bitmask_create_SDL"

I've checked the code and suggest add return statement at end of function.



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Steven Pritchard 2006-03-20 18:52:21 UTC
Please report this issue upstream if the problem is still present in the current
release.

Comment 2 David Binderman 2006-03-20 20:15:23 UTC
(In reply to comment #1)
> Please report this issue upstream if the problem is still present in the current
> release.

Good comedy.

Nothing happens to my bug report for a year, then you expect me to
do something about it ?

Perhaps a reminder that the Fedora project is a volunteer project
might be in order.

Comment 3 Steven Pritchard 2006-03-20 22:04:32 UTC
a) I haven't owned this ticket for very long.
b) This bug report is old, for an old release of FC and supertux.
c) I have no interest in the Intel compiler.  The software's developers might.

I'm sorry if you don't like my response, but I don't want to leave a ticket open
for something that will not be fixed by me.