Aldo Calpini wrote: > > Frazier, Joe Jr wrote: > > > but I still don't know what to do when you just say use Win32::GUI ;-) > > > > <vote type="my opinion">Use old style by default. This avoids users > > having to change thier code until they are ready to totally update thier > > code.</vote> > > yes, this is sure. by default the old style is used, the problem is when you > don't use it and put an -events option on something. maybe I should > process -events options *only* if you said: > > use Win32::GUI Event_Model => 'byref';
Seems like it would be possible to "merge" the old and new styles, if, when a new window or control is defined, a search of the compiled namespace would be done, and all functions defined at that time that match the "window or control name followed by underscore followed by event name" naming convention could be implicitly included into the -event list (unless they were already defined explicitly with a -event or -onEvent parameter). This would allow a gradual migration path from old to new model, for most typical Win32::GUI programs. Programs that use eval to define new methods to handle new events for new windows or controls wouldn't benefit as greatly, but the (few) places where those evals are done could be converted into Change ( -event ) calls. -- Glenn ===== Remember, 84.3% of all statistics are made up on the spot.
