Bug 149527

Summary:	6 * missing return statements
Product:	[Fedora] Fedora	Reporter:	David Binderman <dcb314>
Component:	d4x	Assignee:	Matthias Saou <matthias>
Status:	CLOSED UPSTREAM	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3
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:	2005-05-03 11:49:16 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-02-23 19:57:31 UTC

Description of problem:

I just tried to compile package d4x-2.5.0-2 from 
Redhat Fedora Extras development tree.

The compiler said

list.cc(1220): warning #1011: missing return statement at end of
non-void function "d4x_main_vtoolbar_changed"
list.cc(1228): warning #1011: missing return statement at end of
non-void function "d4x_main_vtoolbar_up"
list.cc(1236): warning #1011: missing return statement at end of
non-void function "d4x_main_vtoolbar_down"
lod.cc(841): warning #1011: missing return statement at end of
non-void function "_real_select_by_wildcard_"
lod.cc(847): warning #1011: missing return statement at end of
non-void function "_real_unselect_by_wildcard_"
lod.cc(1607): warning #1011: missing return statement at end of
non-void function "_foreach_invert_selection_"

It looks like there are a few missing return statements.


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


How reproducible:


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


Expected results:


Additional info:

Comment 1 Matthias Saou 2005-05-03 11:49:16 UTC

Thanks for the bug report.  At the moment, the Fedora developers don't have
time to work on this particular issue. The best way to make sure your problem
will get looked on is to report it to the authors of the program. Most 
upstream authors use a bug tracking system like bugzilla, and more people
who know the code will be looking at the bug report there.

The upstream bug tracking system to use is:
http://www.krasu.ru/soft/chuchelo/forum.php3

Please make sure the bug isn't already in the upstream bug tracker before
filing it.