Bug 288298 - [command] ICommandControlService poorly named?
Summary: [command] ICommandControlService poorly named?
Status: RESOLVED WONTFIX
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug-dsf (show other bugs)
Version: 7.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Pawel Piech CLA
URL:
Whiteboard:
Keywords: api
Depends on:
Blocks:
 
Reported: 2009-09-01 16:10 EDT by John Cortell CLA
Modified: 2009-09-01 17:26 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description John Cortell CLA 2009-09-01 16:10:41 EDT 
Should "Service" be part of the interface name? After all, we don't have IDisassemblyService, IMemoryService, etc.
Comment 1 Pawel Piech CLA 2009-09-01 17:15:34 EDT 
Perhaps it is a poor name since it is not consistent with other service names.  We started with ICommandControl, but we later changed it so that it didn't extend IService.  We did that so that other non-service object could implement it, i.e. MIVariableCache.  It then turned out that having a non-service interface to reference a service was problematic, so we created this ICommandControlService.

In any case, I can't imagine that we would want to break backwards compatibility in a future release just in order to fix this name, so I'm marking as won't fix.
Comment 2 John Cortell CLA 2009-09-01 17:26:30 EDT 
Fair enough. Just wanted to put it on the radar in case there was a bucket of interfaces to rename for a future major release (7.0).