[Mono-bugs] [Bug 49957][Nor] New - Design and implement new Tool Command Language

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Thu, 13 May 2004 15:24:07 -0400 (EDT)

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by miguel@ximian.com.


--- shadow/49957	2004-05-13 15:24:07.000000000 -0400
+++ shadow/49957.tmp.28419	2004-05-13 15:24:07.000000000 -0400
@@ -0,0 +1,52 @@
+Bug#: 49957
+Product: Mono Tasks
+Version: 0%
+OS: unknown
+OS Details: 
+Status: RESOLVED   
+Resolution: FIXED
+Severity: Unknown
+Priority: Normal
+Component: Debugger
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: miguel@ximian.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+Summary: Design and implement new Tool Command Language
+The debugger needs a new tool command language for the interpreter. 
+This should not be based on a pure language like it is now, but rather
+on the notion of commands, and some specific commands might implement
+extended features like C# parsing.
+The general idea is that there is a common tool-like language that
+performs parsing, and grouping, like the Unix shell does, and provides
+the arguments pre-processed, like:
+list file.cs 10-20
+Would invoke the command "list" with the arguments "file.cs" and
+"10-20".  Parsing those is up to each command.
+Maybe we could use attributes to annotate commands, so some common
+tasks can be encapsulated, for example:
+b -option -option2 
+We could define:
+[Name ("break")]
+class Breakpoint : Command {
+     [Option]
+     string option;
+     [Option]
+     string option2;
+     Execute (string [] args) {}
+------- Additional Comments From miguel@ximian.com  2004-05-13 15:24 -------