Another thing being played with. Michael C. has made a Free Pascal Class Chart similar to…
"Michael A. Hess" wrote 17 lines
The class chart is drawn using plain PS, see example below:
%%%%%%%%%%%%%%%%%%%%%%%
% TObject
%%%%%%%%%%%%%%%%%%%%%%%
(TObject) Ready drawlargebox
%%%%%%%%%%%%%%%%%%%%%%%
% Exception classes
%%%%%%%%%%%%%%%%%%%%%%%
(Exception) Ready newchildclass
(EAbort) Incomplete newchildclass
(EAbstractError) Ready newclass
(EAccessViolation) Ready newclass
(EBitsError) Ready newclass
(EConvertError) Ready newclass
(EDatabaseError) Missing newclass
(EDBCLient) Missing newchildclass
(EReconcileError) Missing newchildclass
onelevelback
(EDBEngineError) Missing newclass
(ENoResultSet) Missing newclass
(EUpdateError) Missing newclass
onelevelback
(EDBEditError) Missing newclass
(EDOMError) Ready newclass
(EDomHierarchyRequest) Ready newchildclass
(EDOMIndexSize) Ready newclass
.....
So it should be no problem to keep the k/l/fcl class charts together by simple adding a variable lcl and a procedure lclonly like that:
/lclonly
{
/param exch def
lcl 1 eq { param } if
} def
(Exception) Ready newchildclass
(EAbort) Incomplete newchildclass
(EAbstractError) Ready newclass
{ (ELCLException) Ready newclass } lclonly % this class is only in lcl chart (EAccessViolation) Ready newclass
At the beginning:
/lcl { 1 % set this to zero if you don't want to include the lcl classes } def
so you can easily decide what classes you want to include!
