Feel free to ignore these notes to myself. The takeaway is to focus on what's important, namely the actual checks.
*Maintain code simplicity!* It's easy to get caught up in code cleanup and worries about code speed. They don't matter! I'll tweak the packaging of the command, but I'll leave that for later. *Use regex patterns in the production code?* Patterns are how we think! They are not just a clever coding trick. The ast is needed only to solve *rare* nesting-related issues. *Focus on what's important* The only thing that matters now is completing checks of function calls by checking function calls against their signatures. - It's important to report successful checks, actual errors, and checks that could not be completed due to incomplete data/inferences. - I'll also check the contents of symbol tables. They contain a log of 'unknown' types. That's probably ok. *Other notes* - Naming conventions should include only the *public* interface of Leo's classes, including their "official" ivars. Naming conventions *not* include "private" data. - Per-outline conventions will happen automatically using @data nodes. Per-file naming conventions are possible. - It *might* be possible to check assignments, or make more inferences. - Aha: Leo's conventions eliminate the need for global caches. Edward -- 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 https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
