On 06/21/02 Peter Lillevold wrote: > Well ofcourse, everything you can create using handtyped code and a compiler > can be generated using Reflection.
Barring bugs and omissions, of course. And in Reflection land there are quite a bit of both. For example, you can't create a nested enum. Here is a list of a few other problems: *) no access to volatile modifier (either set or get) *) cannot create a stand-alone module *) cannot _use_ a standalone module *) cannot properly use nested attributes *) cannot produce short code in exceptions (always need to use leave instead of leave.s) *) cannot create a methodref for a method defined in a base class I'm sure miguel has a longer list of the limitations of the API. Next come the different behaviors, for example, of a Type and a TypeBuilder: the semantics of the GetInterfaces() method is completely different even though TypeBuilder derives from Type. And last, there is no efficient method to do some common things such as query an assembly for the namespaces defined in it. It would be good to hear from MS what are the plans for some of this issues, specially the ones that will make a reflection-based compiler produce incorrect code. Thanks. Oh, I should add, I'm quite happy overall with Reflection, it sure was fun implementing it;-) lupus -- ----------------------------------------------------------------- [EMAIL PROTECTED] debian/rules [EMAIL PROTECTED] Monkeys do it better You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
