The BAR object, which is the interfacial object for deserialized data files opened for node editing, allows the user to query information about the implementation file associated with the BAR object.

None of the type lookup functions actually require a BAR object to have a file loaded at the time of the function call. The functions are only designed to report information about the I.F. For this reason, you can get information in BARfly by calling this function when the current view displays either a compiled I.F. or a data file.  You cannot use these functions with an uncompiled I.F.

All the functions are called the same way in BAR and BARfly, with the exception of Read_Global_Buffer.  The function Read_Global_Buffer in BARfly ignores the second parameter, and instead of copying the data to a buffer, a string representing the buffer is displayed.  If you use this function in your own application, you can pass a more varied destination buffer to the function.

The functions you can call by selecting Run.Run BAR Interfacial Function are as follows.

• Get_Construct_Type
• Get_Construct_Child_Count
• Get_Construct_Size
• Get_Construct_Bit_Size
• Get_Construct_Min_Size
• Get_Construct_Min_Bit_Size
• Get_Construct_UID
• Get_Construct_Name
• Get_Construct_Attribute
• Get_Construct_Unit_Type
• Get_Top_Level_UID
• Get_Construct_Child_UID
• Get_Global_Variable_UID
• Get_Member_Variable_UID
• Get_Variable_Name
• Get_Variable_Type
• Read_Global_Long
• Read_Global_Buffer
• Get_Member_Function_UID
• Get_Global_Function_UID
• Get_Function_Name
• Get_Function_Parameter_Count
• Get_Function_Return_Type
• Get_Function_Parameter_Type
• Get_Function_Parameter_Name
• Get_Enum_Block_UID
• Get_Enum_Block_Name
• Get_Enum_Constant
• Get_Enum_Name

  See also:  [BAR_Services Functions] [BAR_Registry Functions] [BAR Functions]