object name limitation

[Haakon Birkeland]

Are there any technical/good reasons to why you have chosen to not allow underscores in the object names? ('Not a legal name').
It's not a problem with PB as I've used it all the time to name the darn number %equates..

And I, for one, have always prefered fx. frm_Main over frmMain as it makes the names (and object types) even more quickly readable.

So if possible, - wishlist item..  

[TechSupport]

This was one of those design decisions that was important in order to facilitate the way way that FireFly names its message functions. eg: FORM1_TEXTBOX1_WM_COMMAND

Will the restriction be lifted? Not at this point. Maybe in the future if the internal parser gets updated then maybe I'll be able to lift the restriction.

Sorry that it impacts your coding style. You can still use it for variables and equates, just not as name properties of objects.