Note: There are a few cases of duplicates in user autocompletion which are being worked on.

init list build warning for mock_Link.h

RESOLVED FIXED in mozilla15

Status

()

Core
DOM
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: dholbert, Assigned: dholbert)

Tracking

(Blocks: 1 bug)

Trunk
mozilla15
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

(Assignee)

Description

5 years ago
Noticed this build warning today:
{
In file included from ../../../../../../toolkit/components/places/tests/cpp/test_IHistory.cpp:12:0:
../../../../../dist/include/mozilla/dom/Link.h: In constructor 'mozilla::dom::Link::Link(mozilla::dom::Element*)':
../../../../../dist/include/mozilla/dom/Link.h:129:8: warning: 'mozilla::dom::Link::mRegistered' will be initialized after
../../../../../dist/include/mozilla/dom/Link.h:121:19: warning:   'mozilla::dom::Element* const mozilla::dom::Link::mElement'
../../../../../../toolkit/components/places/tests/cpp/mock_Link.h:73:1: warning:   when initialized here
}

This is because bug 747516 reordered the member data within the 'Link' structure, without updating the constructor's init list in mock_Link.h.

Trivial fix -- just reorder the init list in mock_Link.h
(Assignee)

Comment 1

5 years ago
Created attachment 626219 [details] [diff] [review]
fix

This moves mLinkState and mRegistered to be after mElement, in mock_Link.h.  

This matches the change made to the member-variable ordering in Link.h -- see the very end of this cset for reference:
 http://hg.mozilla.org/mozilla-central/rev/25f093f5a4bd#l2.2
Attachment #626219 - Flags: review?(ehsan)
Attachment #626219 - Flags: review?(ehsan) → review+
(Assignee)

Comment 2

5 years ago
https://hg.mozilla.org/integration/mozilla-inbound/rev/0cf1ff867a37
Target Milestone: --- → mozilla15

Comment 3

5 years ago
https://hg.mozilla.org/mozilla-central/rev/0cf1ff867a37
Assignee: nobody → dholbert
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.