Bug 889 - poor use of NULL in socketbits.h for gc++
Summary: poor use of NULL in socketbits.h for gc++
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: glibc   
(Show other bugs)
Version: 5.2
Hardware: All Linux
low
low
Target Milestone: ---
Assignee: Cristian Gafton
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-01-20 14:07 UTC by Stephen J. Friedl
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-07-02 20:36:21 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Stephen J. Friedl 1999-01-20 14:07:44 UTC
The file /usr/include/socketbits.h has an inline
routine "__cmsg_nxthdr" that includes "return NULL;"
in its body. Under gc++ this produces: "warning: ANSI C++
forbids implicit conversion from `void *' in return"

The warning is only of minor annoyance, but it can be made
to completely go away for all platforms by chaning
"return NULL;" to "return 0;". C and C++ both say that
trying to "assign" an explicit integral constant zero
to any pointer produces the valid NULL pointer.

Comment 1 Preston Brown 1999-03-22 20:22:59 UTC
Cristian, can you make this small fix please? NULL and c++ == bad.

Comment 2 Cristian Gafton 1999-07-02 20:36:59 UTC
Fixed in the new glibc package. Available from rawhide shortly.


Note You need to log in before you can comment on or make changes to this bug.