-BUGS
-----
-
-* Adding variables.
-
- We do add variables in a number of places, and this is erroneous:
+===========================================
- void a (int b)
- {
- int b;
- }
+* Value Parameter
- Also:
+ I believe that `Value Parameter' might have been introduced
+ after C# 1.0, also notice than in the treatment of Value Parameter
+ the parameters are defined in four categories:
- void a (int b)
- {
- foreach (int b ...)
- ;
- }
+ Section 9.3 in the latest spec.
-* FindMembers
+Large project:
+--------------
- Move our utility FindMembers from TypeContainer to Decl, because interfaces
- are also scanned with it.
+New
+---
- >> DONE - we have separate FindMembers methods for interfaces,
- >> enums, delegates etc.
+ It would be nice to optimize the case of:
-* Visibility
+ Method (new ValueType ())
- I am not reporting errors on visibility yet.
+ So that no temporary is created, and we only use a newobj call
+ that remains on the stack, as opposed to ldloca, initobj, ldloc
+ call.
-* Enumerations
+NEW NOTES:
+----------
- They currently can not be defined in terms of other enumerations
- or constants.
-
- >> DONE
+ ImplicitStandardConversionExists and ImplicitStandardConversion
+ should always be the same, but there are a few diverging lines that
+ must be studied:
-* Interfaces
+ if (expr_type == target_type && !(expr is NullLiteral))
+ return expr;
- 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:
+ vs:
- .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..
- ...
- }
+ if (expr_type == target_type)
+ return true;
-* Interface indexers
+****************************************************************************************
+*
+* The information on the rest of this file is mostly outdated, and its kept here for
+* historical reasons
+*
+****************************************************************************************
+
+Error Reporting:
+----------------
- I have not figured out why the Microsoft version puts an
- `instance' attribute, and I am not generating this `instance' attribute.
+ * Make yyerror show a nice syntax error, instead of the current mess.
- Explanation: The reason for the `instance' attribute on
- indexers is that indexers only apply to instances
+Optimization ideas
+------------------
-* In class.cs: Method.Define
+ Currently when we build a type cache, it contains private members,
+ internal members, and internal protected members; We should trim
+ these out, as it shows up on the profile.
- Need to use FindMembers to lookup the member for reporting
- whether a new is needed or not.
+ We create too many Arraylists; When we know the size, we should create
+ an array;
- >> DONE
+ During parsing we use arraylists to accumulate data, like this:
-* Handle destructors specially
+ thing:
+
+ thing_list
+ : thing { $$ =new ArrayList (); $$.Add ($1); }
+ | thing_list thing { ArrayList a = $1; a.Add ($2); $$ = a; }
- Turn ~X () { a () } into:
- void Finalize () { try { a (); } finally { base.Finalize (); } }
+ We probably could start using "Pairs" there:
-* Method Names
+ thing_list
+ : thing { $$ = new Pair ($1, null); }
+ | thing_list thing { Pair p = $1; $$ = new Pair ($2, $1); }
- Method names could be; `IFACE.NAME' in the method declaration,
- stating that they implement a specific interface method.
- We currently fail to parse it.
+EmitContext.ResolveTypeTree
+---------------------------
-* Namespaces
+ We should investigate its usage. The problem is that by default
+ this will be set when calling FindType, that triggers a more expensive
+ lookup.
- Apparently:
+ I believe we should pass the current EmitContext (which has this turned off
+ by default) to ResolveType/REsolveTypeExpr and then have the routines that
+ need ResolveType to pass null as the emit context.
- namespace X {
- }
+DeclareLocal audit
+------------------
- namespace X {
- }
+ DeclareLocal is used in various statements. The audit should be done
+ in two steps:
- Is failing to create a single namespace
+ * Identify all the declare locals.
- >> This has been fixed. Test #33 tests this functionality
+ * Identify its uses.
-* Arrays
+ * Find if we can make wrapper functions for all of them.
- We need to make sure at *compile time* that the arguments in
- the expression list of an array creation are always positive.
+ Then we can move DeclareLocal into a helper class.
-* Fix access to variables of type ref/out
+ This is required to fix foreach in iterators.
-* Implement dead code elimination in statement.cs
+Ideas:
+------
- It is pretty simple to implement dead code elimination in
- if/do/while
+ Instead of the hack that *knows* about System.Object not having any children classes,
+ we should just make it simple for a probe to know that there is no need for it.
-* Indexer bugs:
+Dead Code Elimination bugs:
+---------------------------
- the following wont work:
+ I should also resolve all the children expressions in Switch, Fixed, Using.
- x [0] = x [1] = N
+Major tasks:
+------------
+ Properties and 17.6.3: Finish it.
- if x has indexers, the value of x [N] set is set to void. This needs to be
- fixed.
-
-* Array declarations
-
- Multi-dim arrays are declared as [,] instead of [0..,0..]
+readonly variables and ref/out
+
+BUGS
+----
* Break/Continue statements
They should transfer control to the finally block if inside a try/catch
block.
-* Conversions and overflow
-
- I am not using the checked state while doing type casts,
- they should result in conv.ovf.XXX
+*
+> // CSC sets beforefieldinit
+> class X {
+> // .cctor will be generated by compiler
+> public static readonly object O = new System.Object ();
+> public static void Main () {}
+> }
+>
PENDING TASKS
-------------
- * Finish Using.
-
- * Implement explicit interface implemenation.
+* Merge test 89 and test-34
- * 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
- * Implement `base' (BaseAccess class)
+* Emit modreq for volatiles
-* Function Declarations
-
- Support PINvoke/Internallcall and extern declarated-functions.
-
-* Manual field layout in structures
-
-* Make the rules for inheritance/overriding apply to
- properties, operators and indexers (currently we only do this
- on methods).
-
-
-* Using Alias
-
- Need to reset the aliases for each compilation unit, so an
- alias defined in a file does not have any effect on another one:
-
- File.cs
- =======
- namespace A {
- using X = Blah;
-
- class Z : X { <-- This X is `Blah'
- }
-
- File2.cs
- namespace {
- class Y : X { <-- This X Is not `Blah'
- }
- }
-
- 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.
-
- The driver advances the Alias for each file compiled, so that each file
- has its own alias set.
-
-* Handle volatile
-
-* Support Re-Throw exceptions:
-
- try {
- X ();
- } catch (SomeException e){
- LogIt ();
- throw;
- }
-
-* Static flow analysis
-
- Required to warn about reachability of code and definite
- assignemt as well as missing returns on functions.
-
-* Implement `goto case expr'
+ Handle modreq from public apis.
+* Merge tree.cs, rootcontext.cs
OPTIMIZATIONS
-------------
-* Emitcontext
-
- Do we really need to instanciate this variable all the time?
-
- 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
+* User Defined Conversions is doing way too many calls to do union sets that are not needed
- Currently I use brfalse/brtrue in the code for statements, instead of
- using the EmitBranchable function that lives in Binary
+* Add test case for destructors
-* Create an UnimplementedExpcetion
+* 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).
- And use that instead of plain Exceptions to flag compiler errors.
+* Dropping TypeContainer as an argument to EmitContext
-* ConvertImplicit
+ 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).
- Currently ConvertImplicit will not catch things like:
-
- - IntLiteral in a float context to generate a -FloatLiteral.
- Instead it will perform an integer load followed by a conversion.
+ The only pending problem is that the code that implements Aliases
+ is on TypeContainer, and probably should go in DeclSpace.
* Tests
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
- That emits the code to call Get and then leaves a this pointer
- 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.
-* Use of temporary values in Assign
+* MakeUnionSet Callers
- We generate suboptimal code for assignments, as we always
- store the result in a temporary.
+ 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.
- When implenenting `using' on
+* Factor the lookup code for class declarations an interfaces
+ (interface.cs:GetInterfaceByName)
- using (a = new XXX)
-
- Two instances of XXX were created, we need to research this.
-
- //
- // FIXME! We need a way to "probe" if the process can
- // just use `dup' to propagate the result.
- //
- // I Think I figured this out, have EmitAssign take an
- // argument: leave result on stack or not. If true,
- // then we can dup ahead of time if we know about this,
- // and we get rid of the temporary value
- //
-
RECOMMENDATIONS
---------------
Notice how numbering of the arguments changes as the
{ oob_stack.Push (lexer.Location) } takes a "slot" in the productions.
-* local_variable_declaration
-
- Not sure that this grammar is correct, we might have to
- resolve this during semantic analysis.
-
-
-* Try/Catch
-
- Investigate what is the right value to return from `Emit' in
- there (ie, for the `all code paths return')
-
-
-* Optimizations
-
- Only create one `This' instance per class, and reuse it.
-
- Maybe keep a pool of constants/literals (zero, 1)?
\ No newline at end of file
projects / mono.git / blobdiff