Closed Bug 329039 Opened 19 years ago Closed 19 years ago

make nsIOService's ctor and dtor private

Categories

(Core :: Networking, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla1.8.1

People

(Reporter: Biesinger, Assigned: Biesinger)

Details

(Keywords: fixed1.8.1)

Attachments

(1 file)

No point in having them public.
Attached patch patchSplinter Review
this makes the compiler ensure that there can only be one instance of the io service.
Attachment #213683 - Flags: superreview?
Attachment #213683 - Flags: review?(darin)
Attachment #213683 - Flags: approval-branch-1.8.1?(darin)
Attachment #213683 - Flags: superreview?
Attachment #213683 - Flags: superreview+
Attachment #213683 - Flags: review?(darin)
Attachment #213683 - Flags: review+
Attachment #213683 - Flags: approval-branch-1.8.1?(darin)
Attachment #213683 - Flags: approval-branch-1.8.1+
Actually, if the ctor/dtor are private, then having protected sections doesn't make any sense either. You might therefore want to make the protected sections private as well.
fixed, with private. HEAD: Checking in netwerk/base/src/nsIOService.h; /cvsroot/mozilla/netwerk/base/src/nsIOService.h,v <-- nsIOService.h new revision: 1.58; previous revision: 1.57 done MOZILLA_1_8_BRANCH: Checking in netwerk/base/src/nsIOService.h; /cvsroot/mozilla/netwerk/base/src/nsIOService.h,v <-- nsIOService.h new revision: 1.55.2.3; previous revision: 1.55.2.2 done
Status: NEW → RESOLVED
Closed: 19 years ago
Keywords: fixed1.8.1
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.8.1
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: