1.1 --- a/TO_DO.txt Tue Aug 31 00:59:16 2010 +0200
1.2 +++ b/TO_DO.txt Sat Sep 04 00:55:37 2010 +0200
1.3 @@ -1,7 +1,20 @@
1.4 +Support slicing. This is difficult because __getitem__ has to handle integers and slice
1.5 +objects differently. One could either just try and iterate over the argument and then
1.6 +catch the AttributeError for integers, or one could test the instances first.
1.7 +
1.8 +Support isinstance. Like slicing, the problem is dealing with the class or tuple input
1.9 +to the function. A strict tuple check is permissible according to the CPython behaviour,
1.10 +but an iterable would be more elegant (as would *args).
1.11 +
1.12 +Consider attribute usage observations being suspended inside blocks where AttributeError
1.13 +may be caught (although this doesn't anticipate such exceptions being caught outside a
1.14 +function altogether).
1.15 +
1.16 Fix object table entries for attributes not provided by any known object, or provide an
1.17 error, potentially overridden by options. For example, the augmented assignment methods
1.18 are not supported by the built-in objects and thus the operator module functions cause
1.19 -the compilation to fail.
1.20 +the compilation to fail. Alternatively, just supply the methods since something has to do
1.21 +so in the builtins.
1.22
1.23 Support tuple parameters.
1.24
1.25 @@ -45,8 +58,6 @@
1.26
1.27 __getitem__ could be written in Python, using a native method only to access fragments.
1.28
1.29 -Support slicing.
1.30 -
1.31 Consider better "macro" support where new expressions need to be generated and processed.
1.32
1.33 **** Constant attribute users need not maintain usage since they are already resolved. ****