</ul>
+<a name="tasks">
** Current pending tasks
- Array declarations are currently being ignored,
+ Simple tasks:
- PInvoke is not supported.
+ <ul>
+ * Array declarations are currently being ignored,
+
+ * PInvoke declarations are not supported.
+
+ * Pre-processing is not supported.
+
+ * Attribute declarations and passing currently ignored.
- Pre-processing is not supported.
+ * Compiler does not pass around line/col information from tokenizer for error reporting.
- Attribute declarations and passing currently ignored.
+ * Jay does not work correctly with `error'
+ productions, making parser errors hard to point. It
+ would be best to port the Bison-To-Java compiler to
+ become Bison-to-C# compiler (bjepson@oreilly.com
+ might have more information)
+ </ul>
+
+ Critical tasks:
- Compiler does not pass around line/col information from tokenizer for error reporting.
+ <ul>
+ * Resolve "base" classes and "base" interfaces for
+ classes, structs and interfaces.
- Jay does not work correctly with `error' productions, making parser errors hard to point.
+ Once this is done, we can actually do the semantic
+ analysis, because otherwise we do not know who our
+ parents are.
+ </ul>
** Questions and Answers
Mono-based solution. Some of these tools can be developed on
Windows before Mono is fully finished.
+** Debugger
+
+ We will need a debugging API to debug CLI applications and
+ then a debugger component that can be used in an IDE
+ environment.
+
** Integrated Development Environment
There is already a project to create a C# development
</ul>
+<a name="tasks">
** Current pending tasks
- Array declarations are currently being ignored,
+ Simple tasks:
- PInvoke is not supported.
+ <ul>
+ * Array declarations are currently being ignored,
+
+ * PInvoke declarations are not supported.
+
+ * Pre-processing is not supported.
+
+ * Attribute declarations and passing currently ignored.
- Pre-processing is not supported.
+ * Compiler does not pass around line/col information from tokenizer for error reporting.
- Attribute declarations and passing currently ignored.
+ * Jay does not work correctly with `error'
+ productions, making parser errors hard to point. It
+ would be best to port the Bison-To-Java compiler to
+ become Bison-to-C# compiler (bjepson@oreilly.com
+ might have more information)
+ </ul>
+
+ Critical tasks:
- Compiler does not pass around line/col information from tokenizer for error reporting.
+ <ul>
+ * Resolve "base" classes and "base" interfaces for
+ classes, structs and interfaces.
- Jay does not work correctly with `error' productions, making parser errors hard to point.
+ Once this is done, we can actually do the semantic
+ analysis, because otherwise we do not know who our
+ parents are.
+ </ul>
** Questions and Answers
Mono-based solution. Some of these tools can be developed on
Windows before Mono is fully finished.
+** Debugger
+
+ We will need a debugging API to debug CLI applications and
+ then a debugger component that can be used in an IDE
+ environment.
+
** Integrated Development Environment
There is already a project to create a C# development