[cdt-debug-dev] CommandFactory and "missing" createMIBreakpoint

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[cdt-debug-dev] CommandFactory and "missing" createMIBreakpoint

From: Øyvind Harboe <oyvind.harboe@xxxxxxxxx>
Date: Wed, 18 May 2005 14:47:28 +0200
Delivered-to: cdt-debug-dev@xxxxxxxxxxx
List-archive: <http://eclipse.org/pipermail/cdt-debug-dev>
List-help: <mailto:cdt-debug-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev>, <mailto:cdt-debug-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev>, <mailto:cdt-debug-dev-request@eclipse.org?subject=unsubscribe>

Is MIBreakpoint left out by design from CommandFactory?


I want to create a subclass of  the CommandFactory in the EmbeddedCDT
plugin to move hacks out of CDT and into the plugin. MIBreakpoint is one
of the classes that need CygWin hacks.

These classes(so far), contain CygWin path hacks:


MIBreakpoint.java
MIConst.java
MIFrame.java
MIParser.java
MISrcAsm.java

-- 
Øyvind Harboe
http://www.zylin.com

Prev by Date: Re: [cdt-debug-dev] Cursor position in memory view
Next by Date: [cdt-debug-dev] Eclipse M7 & CDT
Previous by thread: [cdt-debug-dev] Cursor position in memory view
Next by thread: [cdt-debug-dev] Eclipse M7 & CDT
Index(es):
- Date
- Thread

Breadcrumbs