Third-party dependencies Report

Top Previous Next

[BP7,D1,D2,D3,D4,D5,D6,D7,D8, D2005W, D2005N, D2006W, D2006N, D2007W, D2009W, D2010W, DXEW]

This report has four sections:

Third-party folders directly referenced

Third-party units directly referenced

Third-party identifiers directly referenced

Third-party identifiers directly referenced, with locations

All code is considered to be third-party (external), if it is located in a folder that is different than the folder for the project main file. Possibly this will also include code that is not really third-party (external), but your own.

The report will give you an overview of how your code depends on third-party code. You may for example discover that a particular set of third-party code is only used briefly. In that case you may decide to replace it to get rid of the dependency.

The report sections “Third-party identifiers directly referenced” and “Third-party identifiers directly referenced, with locations” include ALL found identifiers, even those that are located in folders that are excluded for reporting. The reason for this is that you otherwise would have to include these folders to get this information, leading to much bigger lists.

****************************************************************************

* Third-party dependencies Report for *

* C:\PROJEKT\PIM\EPA.DPR *

****************************************************************************

(9) Third-party folders directly referenced:

----------------------------------------------------------------------------

C:\Program Files\FastReports\FastReport\Source

D:\3rdParty\TurboPower\Orpheus\source

D:\3rdParty\TurboPower\ShellShock\source

D:\3rdParty\TurboPower\SysTools\source

D:\3rdParty\VirtualTreeview

(36) Third-party modules directly referenced:

----------------------------------------------------------------------------

BAbout

BCat

BFile

BGlobals

BGuard

BIcon

BRes

BTodo

BUtils