Hidden under the myriad of Android docs is a gem for anyone writing embedded Java applications: Writing Efficient Android Code.
While some of the concepts there presented would make many a software architect/OO practitioner cringe (Prefer Virtual Over Interface?), the writer is careful enough to advise when (or when not) to do something.
And speaking of gems, I found another presentation that describes how you can use Eclipse CDT to introspect C source code a la DOM. It even describes how the Eclipse Parallel Tools Platform (PTP) project used it to implement some neat features such as barrier analysis, call graph, and identifying potential deadlocks. Pretty exciting for me... having a DOM AST available opens up a lot of possibilities. Think code metrics, static code analysis, visualization, refactoring, etc. integrated into the same IDE in which you write the code.
No comments:
Post a Comment