> > > Large API. Honestly what is the main requirement for a reflection API. > Do you really need information on the calling convention of a > function, etc. or do people just want to iterate over the members of a > struct? > > -- James > > Well, that would really depend on the use case, no? If you want to do metaprogramming (or rather validation of generated/imported code) I'd say the more info the merrier. Basically, if it can be exposed I don't see why you wouldn't reflect it - I'd rather have too much info available than too little.