From f8934d49d715f5df05da243e00f5248d1ffc7461 Mon Sep 17 00:00:00 2001 From: Marc Khouzam Date: Wed, 2 Apr 2008 15:18:36 +0000 Subject: [PATCH] Comment no longer valid after fix of Bug 206932 --- .../src/org/eclipse/dd/mi/service/MIVariableManager.java | 8 -------- 1 file changed, 8 deletions(-) diff --git a/plugins/org.eclipse.dd.mi/src/org/eclipse/dd/mi/service/MIVariableManager.java b/plugins/org.eclipse.dd.mi/src/org/eclipse/dd/mi/service/MIVariableManager.java index 5419f125828..44c63630551 100644 --- a/plugins/org.eclipse.dd.mi/src/org/eclipse/dd/mi/service/MIVariableManager.java +++ b/plugins/org.eclipse.dd.mi/src/org/eclipse/dd/mi/service/MIVariableManager.java @@ -85,14 +85,6 @@ import org.eclipse.dd.mi.service.command.output.MIVarUpdateInfo; /** * Manages a list of variable objects as created through GDB/MI commands. * - * Note that for the moment, this class is inheriting from AbstractDsfService, - * although it does not register as a service. This class is only used by the Expression - * Service, and therefore, need not be a service of its own. - * However, to be able to implement ICommandControl, we automatically must implement - * IDsfService, so, that is why we extend AbstractDsfService. We must implement - * ICommandControl service, to be able to interface properly with the MICommandCache which - * is using this class. - * * This class is passed expression-meta-commands which have their own cache. * Therefore, we don't use the standard MICommandCache in this class. * In fact, we can't even use it, because many variableObject MI commands,