> I am focusing on the simplest useful tools that might detect *some* kinds of errors.
> I was generalizing. So what kind of errors would you detect? Also you say about code that handles run time type changes: " Indeed, *all* of Leo's functions and methods will quickly fail if they do not, in fact, receive arguments of the expected types. I assert (without proof ) that in this respect Python and C programs are similar." I was thinking about code that is written generically for types and during run time the types determine what code is run, and the types are passed in during run time, not compile type. In C the types are set-up and in run-time perhaps different paths can be taken but it still -seems- more set-up for the types at build time. Anyway, you have not designed any static-type-checking code yet? Just curious. Todd. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
