Compiler warnings in <nsHashtable.h>: "should be explicitly initialized in the copy constructor"

RESOLVED WORKSFORME

Status

()

Core
XPCOM
RESOLVED WORKSFORME
15 years ago
7 years ago

People

(Reporter: tenthumbs, Unassigned)

Tracking

(Blocks: 1 bug, {helpwanted})

Trunk
mozilla1.5alpha
x86
Linux
helpwanted
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [build_warning])

(Reporter)

Description

15 years ago
In a Linux build from this morning using gcc 3.2.2, I get these warnings.

 dist/include/xpcom/nsHashtable.h:219: warning: base class `class nsHashKey' \
   should be explicitly initialized in the copy constructor

 dist/include/xpcom/nsHashtable.h:288: warning: base class `class nsHashKey' \
   should be explicitly initialized in the copy constructor

 dist/include/xpcom/nsHashtable.h:327: warning: base class `class nsHashKey' \
   should be explicitly initialized in the copy constructor

Since this file is used in many places there are 402 instances of each warning.
I don't know how important this is.

Comment 1

15 years ago
-> alecf
Assignee: dougt → alecf

Comment 2

15 years ago
I welcome any patches here.
Status: NEW → ASSIGNED
Keywords: helpwanted
Target Milestone: --- → mozilla1.5alpha

Updated

15 years ago
Blocks: 187528
Summary: Compiler warnings in nsHashtable.h → Compiler warnings in <nsHashtable.h>: "should be explicitly initialized in the copy constructor"

Comment 3

15 years ago
I'm not an expert in these things, but tinderbox Linux brad Clbr runs gcc 3.3
and seems not to issue those warnings.
Can anybody confirm this or the existence of those warnings?
Assignee: alecf → nobody
Status: ASSIGNED → NEW
QA Contact: scc → xpcom

Updated

7 years ago
Whiteboard: [build_warning]

Comment 4

7 years ago
I could not see any warning in nsHashtable.h file anymore. Also I searched for warning in nightly builds of mac, windows and linux and could not find one. Hence closing this bug.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.