There are several different types of file information views.  Each view reports information specific to the file type (registry, I.F., or data file) as plain text.  To invoke a file information view, select the Information.Show File Info menu item.  The menu item is only available when the current view in the data display window describes a file.

Data Files

The picture to the left is an example of a file info view for a data file.   The filename, file attributes, and time/date stamps are displayed in the data display window, followed by the size of the file (in bytes and bits) on the disk.  This information describes the file as it exists on the disk.  This means the information might not be up-to-date if the data file has been edited in BARfly, but not yet saved.

The file type and whether the file is up-to-date (whether last BARfly edits were saved or not) are reported next.

Finally, BARfly reports the I.F. used as a schema source for the data file.  This will be either a stand-alone I.F. or an embedded file in a registry.

Implementation Files

The picture to the left is an example of a file info view for an implementation file.   The filename, file attributes, and time/date stamps are displayed in the data display window, followed by the size of the file (in bytes and bits) on the disk.  This information describes the file as it exists on the disk.  This means the information might not be up-to-date if the I.F. file has been edited in BARfly, but not yet saved.

The file type and whether the file is up-to-date (whether last BARfly edits were saved or not) are reported next.

BARfly also reports the compiled status of the I.F.  The I.F. can be text-only, binary-only, or mixed text and binary.  If an I.F. is text-only, no further information is reported.  For binary or mixed implementation files, though, a great deal of additional information is reported.

The "compiled file information" reported is as follows:  enumerated constant blocks, global functions, global variables, and construct declarations.  In each case, the unique identifier (UID) of the enumerated constant block, global function, global variable, or construct is reported before the actual declaration.  With this view, it is possible to understand much about the inner workings of an I.F. even if only a binary-only version of the I.F. is available.

The "compiled file information" does not extend to the contents of individual function bodies.   A compiled function body is stored in the form of nonsensical opcodes, so it is not value-added to report such information.

Registry Files

The picture to the left is an example of a file info view for a registry file.   The filename, file attributes, and time/date stamps are displayed in the data display window, followed by the size of the file (in bytes and bits) on the disk.  This information describes the file as it exists on the disk.  This means the information might not be up-to-date if the registry file has been edited in BARfly, but not yet saved.

The file type and whether the file is up-to-date (whether last BARfly edits were saved or not) are reported next.

BARfly identifies the contents of the registry in the following lines.  This includes the zero-based index of each file stored in the registry, plus the contents of the VERSION, FILEEXTENSIONS, FILETYPE, and FILEDESCRIPTION control variables for each file.

  See also: [Viewing node information] [Viewing the log] [Viewing memory blocks]
[Construct hierarchy diagrams] [Determining I.F. protocol support] [Load/Save failure reporting]