J
Jeff Ledbetter
Guest
With regards to #2: WRX reference. Currently, the only way to determine if a window contains a WRX file is to call adeuib/_uibinfo.p (without parsing). Including the WRX reference in the xref output seems like a natural extension to the current output. RUN reference. The only reference to an internal procedure in the current xref output, are the PROCEDURE and PRIVATE-PROCEDURE tokens. These tell us if the compile unit contains an internal procedure, however the RUN of an internal procedure (in the same compile unit) is not represented. If the compile unit containing the procedure definition also contains a RUN for that same procedure, we would like to see a separate RUN reference in the xref listing. IMAGE reference. An IMAGE token that represents a referenced image file (such as in the IMAGE-UP, IMAGE-DOWN, and IMAGE-INSENSITVE options of DEFINE BUTTON statement) would be a welcome addition. OS-COMMAND reference. An indication of the existence of the OS-COMMAND statement in a compile unit would be a welcome addition. Finally, it would be handy it one could optionally choose to not generate STRING references. Jeff Ledbetter www.roundtable-software.com email: jeff.ledbetter@roundtable-software.com skype: jeff.ledbetter From: Garry Hall [mailto:bounce-gih@community.progress.com] Sent: Monday, March 23, 2015 3:55 PM To: TU.OE.Development@community.progress.com Subject: [Technical Users - OE Development] XREF Improvements - Community input is requested XREF Improvements - Community input is requested Thread created by Garry Hall In a similar vein to the recent "Strict mode for the ABL Compiler" thread ( https://community.progress.com/community_groups/openedge_development/f/19/t/16733.aspx?pi20882=1#59978 ), we have received requests for enhancements to XREF. The 11.6 Product Enhancements forum had a thread on XREF enhancements ( https://community.progress.com/community_groups/products_enhancements/i/openedge_116_community_input/add_now_compiler_option_to_output_index_information_on_all_static_queries.aspx ). The following requests were made in this thread: 1) Exposing SEARCH information for local temp-tables. There is a proposal in the thread to address this. 2) Expanding XREF "to cover other things that are local to a given program". What things are missing for local entities? 3) Providing an "explain plan" (bracketing information) on queries, to make it easier to identify potentially bad queries. I have been working on an initial proposal for this, but I don't want to hold up this discussion waiting on it. I would appreciate your input on these topics, and would like to hear any other input you have for XREF enhancements. Thanks, Garry Hall. OpenEdge Development Progress Software Stop receiving emails on this subject. Flag this post as spam/abuse.
Continue reading...
Continue reading...