-BUGS
-----
+TODO:
-* Adding variables.
+ 1. Create a "partial" emit context for each TypeContainer..
- We do add variables in a number of places, and this is erroneous:
+ 2. EmitContext should be partially constructed. No IL Generator.
- void a (int b)
- {
- int b;
- }
+ Optimize the internal type expressions in the parser (system_object, etc)
+ to be something other than DecomposeQI-based expressions.
- Also:
+ interface_type review.
- void a (int b)
- {
- foreach (int b ...)
- ;
- }
+ parameter_array, line 952: `note: must be a single dimension array type'. Validate this
+Dead Code Elimination bugs:
+---------------------------
-* FindMembers
+ I should also resolve all the children expressions in Switch, Fixed, Using.
- Move our utility FindMembers from TypeContainer to Decl, because interfaces
- are also scanned with it.
+Major tasks:
+------------
-* Visibility
+ Pinned and volatile require type modifiers that can not be encoded
+ with Reflection.Emit.
- I am not reporting errors on visibility yet.
+ Properties and 17.6.3: Finish it.
-* Enumerations
+ Implement base indexer access.
- They currently can not be defined in terms of other enumerations
- or constants.
+readonly variables and ref/out
+
+BUGS
+----
-* Interfaces
+* We suck at reporting what turns out to be error -6. Use the standard error message
+ instead.
- For indexers, the output of ix2.cs is different from our
- compiler and theirs. They use a DefaultMemberAttribute, which
- I have yet to figure out:
+* Explicit indexer implementation is missing.
- .class interface private abstract auto ansi INTERFACE
- {
- .custom instance void [mscorlib]System.Reflection.DefaultMemberAttribute::.ctor(string)
- = ( 01 00 04 49 74 65 6D 00 00 ) // ...Item..
- ...
- }
+* Check for Final when overriding, if the parent is Final, then we cant
+ allow an override.
* Interface indexers
Explanation: The reason for the `instance' attribute on
indexers is that indexers only apply to instances
-* In class.cs: Method.Define
-
- Need to use FindMembers to lookup the member for reporting
- whether a new is needed or not.
-
-* Foreach on structure returns does not work
-
- I am generating invalid code instead of calling ldarga for the
- structure, I am calling ldarg:
-
- struct X {
- public IEnumerator GetEnumerator ();
- }
-
- X x;
-
- foreach (object a in x){
- ...
- }
-
- I need to get the address of that bad boy
-
-* Handle destructors specially
-
- Turn ~X () { a () } into:
- void Finalize () { try { a (); } finally { base.Finalize (); } }
+* Indexer bugs:
-* Method Names
+ the following wont work:
- Method names could be; `IFACE.NAME' in the method declaration,
- stating that they implement a specific interface method.
+ x [0] = x [1] = N
- We currently fail to parse it.
+ if x has indexers, the value of x [N] set is set to void. This needs to be
+ fixed.
-* Namespaces
+* Array declarations
- Apparently:
+ Multi-dim arrays are declared as [,] instead of [0..,0..]
- namespace X {
- }
+* Break/Continue statements
- namespace X {
- }
+ A finally block should reset the InLoop/LoopBegin/LoopEnd, as
+ they are logically outside the scope of the loop.
- Is failing to create a single namespace
+* Break/continue part 2.
-* Arrays
+ They should transfer control to the finally block if inside a try/catch
+ block.
- We need to make sure at *compile time* that the arguments in
- the expression list of an array creation are always positive.
+* Method Registration and error CS111
-* Fix access to variables of type ref/out
+ The way we use the method registration to signal 111 is wrong.
+
+ Method registration should only be used to register methodbuilders,
+ we need an alternate method of checking for duplicates.
-* Implement dead code elimination in statement.cs
+* We need to catch:
- It is pretty simple to implement dead code elimination in
- if/do/while
+ extern string Property {
+ get { }
+ }
-* Indexer bugs:
+ The get there should only have a semicolon
+
+*
+> // CSC sets beforefieldinit
+> class X {
+> // .cctor will be generated by compiler
+> public static readonly object O = new System.Object ();
+> public static void Main () {}
+> }
+>
- the following wont work:
+PENDING TASKS
+-------------
- x [0] = x [1] = N
+* IMprove error handling here:
- if x has indexers, the value of x [N] set is set to void. This needs to be
- fixed.
+ public static Process ()
-* Array declarations
+ THat assumes that it is a constructor, check if its the same name
+ as the class, if not report a different error than the one we use now.
- Multi-dim arrays are declared as [,] instead of [0..,0..]
+* Merge test 89 and test-34
+* Revisit
-PENDING TASKS
--------------
+ Primary-expression, as it has now been split into
+ non-array-creation-expression and array-creation-expression.
+
+* Static flow analysis
- * Implement Using.
+ Required to warn about reachability of code and definite
+ assignemt as well as missing returns on functions.
- * Implement Goto.
+* Code cleanup
- * Unsafe code.
+ The information when registering a method in InternalParameters
+ is duplicated, you can always get the types from the InternalParameters
-* Function Declarations
+* Emit modreq for volatiles
- Support PINvoke/Internallcall and extern declarated-functions.
+ Handle modreq from public apis.
-* Manual field layout in structures
+* Emit `pinned' for pinned local variables.
-* Make the rules for inheritance/overriding apply to
- properties, operators and indexers (currently we only do this
- on methods).
+ Both `modreq' and pinned will require special hacks in the compiler.
+* Make sure that we are pinning the right variable
-* Using Alias
+* Maybe track event usage? Currently I am not tracking these, although they
+ are fields.
- Need to reset the aliases for each compilation unit, so an
- alias defined in a file does not have any effect on another one:
+* Merge tree.cs, rootcontext.cs
- File.cs
- =======
- namespace A {
- using X = Blah;
+OPTIMIZATIONS
+-------------
- class Z : X { <-- This X is `Blah'
- }
+* Implement loop inversion for `For' as well.
- File2.cs
- namespace {
- class Y : X { <-- This X Is not `Blah'
- }
- }
+* There is too much unshared code between MemberAccess.Resolve and SimpleName
+ resolve.
+
+* User Defined Conversions is doing way too many calls to do union sets that are not needed
- I think we can implement Aliases by having an `Alias' context in all
- the toplevel TypeContainers of a compilation unit. The children typecontainers
- just chain to the parents to resolve the information.
+* Add test case for destructors
- The driver advances the Alias for each file compiled, so that each file
- has its own alias set.
+* Places that use `Ldelema' are basically places where I will be
+ initializing a value type. I could apply an optimization to
+ disable the implicit local temporary from being created (by using
+ the method in New).
-* Handle volatile
+* Dropping TypeContainer as an argument to EmitContext
-* Support Re-Throw exceptions:
+ My theory is that I can get rid of the TypeBuilder completely from
+ the EmitContext, and have typecasts where it is used (from
+ DeclSpace to where it matters).
- try {
- X ();
- } catch (SomeException e){
- LogIt ();
- throw;
- }
+ The only pending problem is that the code that implements Aliases
+ is on TypeContainer, and probably should go in DeclSpace.
-* Static flow analysis
+* Casts need to trigger a name resolution against types only.
- Required to warn about reachability of code and definite
- assignemt as well as missing returns on functions.
+ currently we use a secret hand shake, probably we should use
+ a differen path, and only expressions (memberaccess, simplename)
+ would participate in this protocol.
+* Use of local temporary in UnaryMutator
-OPTIMIZATIONS
--------------
+ We should get rid of the Localtemporary there for some cases
* Emitcontext
It could be static for all we care, and just use it for making
sure that there are no recursive invocations on it.
-* Static-ization
-
- Since AppDomain exists, maybe we can get rid of all the stuff
- that is part of the `compiler instance' and just use globals
- everywhere.
-
-
-* Constructors
-
- Currently it calls the parent constructor before initializing fields.
- It should do it the other way around.
-
-* Reducer and -Literal
-
- Maybe we should never handle -Literal in Unary expressions and let
- the reducer take care of it always?
-
* Use of EmitBranchable
Currently I use brfalse/brtrue in the code for statements, instead of
using the EmitBranchable function that lives in Binary
-* Create an UnimplementedExpcetion
-
- And use that instead of plain Exceptions to flag compiler errors.
-
* ConvertImplicit
Currently ConvertImplicit will not catch things like:
Write tests for the various reference conversions. We have
test for all the numeric conversions.
-* Remove the tree dumper
-
- And make all the stuff which is `public readonly' be private unless
- required.
-
* Optimizations
In Indexers and Properties, probably support an EmitWithDup
in the stack, so that later a Store can be emitted using that
this pointer (consider Property++ or Indexer++)
+* Optimizations: variable allocation.
+
+ When local variables of a type are required, we should request
+ the variable and later release it when we are done, so that
+ the same local variable slot can be reused later on.
* Add a cache for the various GetArrayMethod operations.
-
+
+* TypeManager.FindMembers:
+
+ Instead of having hundreds of builder_to_blah hash table, have
+ a single one that maps a TypeBuilder `t' to a set of classes
+ that implement an interface that supports FindMembers.
+
+* MakeUnionSet Callers
+
+ If the types are the same, there is no need to compute the unionset,
+ we can just use the list from one of the types.
+
+* Factor all the FindMembers in all the FindMembers providers.
+
+* Factor the lookup code for class declarations an interfaces
+ (interface.cs:GetInterfaceByName)
+
RECOMMENDATIONS
---------------
Not sure that this grammar is correct, we might have to
resolve this during semantic analysis.
+* Idea
+
+ MethodGroupExpr
+
+ These guys should only appear as part of an Invocation, so we
+ probably can afford to have a special callback:
+
+ Expression.ResolveAllowMemberGroups
+
+ This is only called by Invocation (or anyone that consumes
+ MethodGroupExprs)
+
+ And the regular DoResolve and DoResolveLValue do emit the error
+ 654 `Method referenced without argument list'.
+ Otherwise, a resolution will return a MethodGroupExpr which is
+ not guaranteed to have set its `Expression.Type' to a non-null
+ value.