Closed Bug 197048 Opened 22 years ago Closed 13 years ago

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

Categories

(Core :: XPCOM, defect)

Product:
Core
Component:
XPCOM
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: tenthumbs, Assigned: jag+mozilla)

References

(Blocks 1 open bug)

Details

(Whiteboard: [build_warning])

On Linux using gcc3.2.2 on a fresh tree from this morning, there are these messages. dist/include/string/nsSharableString.h:117: warning: base class \ `class nsAFlatCString' should be explicitly initialized in the \ copy constructor dist/include/string/nsSharableString.h:55: warning: base class \ `class nsAFlatString' should be explicitly initialized in the \ copy constructor Since this file is used all over there are 1203 instances of each warning. That's 18% of all build warnings not involving unused objects. Gcc is trying to tell us something here and it shouldn't be ignored. I have no idea how strings work so I have no idea how to fix this.
Blocks: buildwarning
Summary: Compiler warnings in nsSharableString.h → Compiler warnings in <nsSharableString.h>: "should be explicitly initialized in the copy constructor"
QA Contact: scc → string
Whiteboard: [build_warning]
I could not see any such error in current code base. Moreover such warnings does not exists in nightly builds also (mac, windows, linux). Hence closing this bug.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
Component: String → XPCOM
You need to log in before you can comment on or make changes to this bug.