onEntry() fills out the tool kit a little. At the activity level, Library code is loaded first, includes are loaded on demand, and onEntry() is executed last. onEntry() is slightly different because it is a function while the other facilities simply copy text.

While heavily "class" oriented programmer would want to define a page class with a start-up constructor, I think that onEntry() is a clean construct to initialize a page loop. I always thought that fussing with an activity global variable or a System global to initialize a page loop was inelegant.

Overall, I spend a major part of my coding time working around the lack of a truly global scope. Yes, moving to a global scope model at this point would introduce potential compatibility issues with existing code, but this could be handled with an "advanced" or "executive" mode switch at the editor level. In "executive" mode onEntry() is a very clean construct.