On 11-05-01 02:21 PM, John McCall wrote: > The convention is that methods which access data which is only valid in > certain configurations of the AST node they're on should be named to > make that clear, and unless there's a good reason not to, they should > assert on that to catch bugs. Obviously those aren't universally followed, > but more consistent is better.
Ah, ok. Sounds good then. > You don't need to give multiple errors, but you do need the compiler > not to hang indefinitely because (1) it keeps finding Targets but > (2) none of them are Constructor. My example currently hangs > the compiler. Please fix this. Ooh, that's bad. Do you think it's better to track every constructor or just set a maximum depth (10? 100 given the cheapness of an iteration?)? > Joh. Sea _______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
