delphidoc-news

[DelphiDoc-News] (no subject)

[vaa20003 <vaa...@ya...>]

Delphi 7=2E

At compilation of the project there is a mistake in the module Delphi ExtA=
ctns in function
function DWordEnumToPascalEnumOrd (EnumArray: array of DWORD; Value: DWORD=
): Integer;
begin
  for Result: =3D Low (EnumArray) to High (EnumArray) do
    if Value =3D EnumArray [Result] then Exit;
  raise Exception=2E CreateRes (@SInvalidEnumValue);
end;

The is the no overloaded version of CreateRes then can be called with thes=
e arguments

[DelphiDoc-News] (no subject)

[vaa20003 <vaa...@ya...>]

Delphi 7

Has disconnected check @ - beginning to compile further but

var       Positions      :PPoint;        //the positions of all files (boxes)
          Files          :^TPascalFile;  //the list of all written files
          NextUnit       :TPoint;        //position of the next file to write


 {Draws a file at the current position and moves the pointer for the next one.
 ~param Index          index in the list of files
 ~param CountPerColumn number of files in a column; 0: as many as fit }
 procedure DrawFile(Index: Cardinal; CountPerColumn: Cardinal = 0);
 var       FileP      :^TPascalFile;     //entry in list of written files
           PositionP  :PPoint;           //entry in list of positions of files
 begin
  PositionP := Positions;
  inc(PositionP, Index);
  if PositionP.x = -1 then               //file not yet written?
   begin
    FileP := Files; - write thet incompatibile type
   
   I do not understand!

Best regard
Alex.

vaa...@ya...

Re: [DelphiDoc-News] Typed Pointers

[Gerold V. <Del...@gm...>]

vaa20003 wrote:
> Has disconnected check @ - beginning to compile further but
> 
> var       Positions      :PPoint;        //the positions of all files (boxes)
>           Files          :^TPascalFile;  //the list of all written files
>           NextUnit       :TPoint;        //position of the next file to write
> 
>  {Draws a file at the current position and moves the pointer for the next one.
>  ~param Index          index in the list of files
>  ~param CountPerColumn number of files in a column; 0: as many as fit }
>  procedure DrawFile(Index: Cardinal; CountPerColumn: Cardinal = 0);
>  var       FileP      :^TPascalFile;     //entry in list of written files
>            PositionP  :PPoint;           //entry in list of positions of files
>  begin
>   PositionP := Positions;
>   inc(PositionP, Index);
>   if PositionP.x = -1 then               //file not yet written?
>    begin
>     FileP := Files; - write thet incompatibile type
> 
>    I do not understand!

You have to use typed pointers to compile DelphiDoc. Either use the project
options to set it or use the compiler comment {$T+} or {$TYPEDADDRESS ON}
in each file. 

This error happens because ^TPascalFile and ^TPascalFile are two different
types for the compiler (see in Delphi's help file on "$T"). A solution
would be to declare the 

type PPascalFile = ^TPascalFile;

and use it instead of the different occurences of ^TPascalFile. 

I (personally) strongly suggest to enable the type check of the pointers in
every project.


Regards, Gerold Veith

Re: [DelphiDoc-News] Overloaded functions

[Gerold V. <Del...@gm...>]

vaa20003 wrote:
> At compilation of the project there is a mistake in the module Delphi
> ExtActns in function
> function DWordEnumToPascalEnumOrd (EnumArray: array of DWORD; 
>                                    Value: DWORD): Integer;
> begin
>   for Result: = Low (EnumArray) to High (EnumArray) do
>     if Value = EnumArray [Result] then Exit;
>   raise Exception. CreateRes (@SInvalidEnumValue);
> end;
> 
> The is the no overloaded version of CreateRes then can be called 
> with these arguments

DelphiDoc is not a Compiler. It has only the information of the files it
parses. So it does not know all identifiers and types (DWORD is f.i. only
known if the unit Windows is also parsed). Overloaded functions are
selected by the number and types of the parameters. For this reason
DelphiDoc can't pick the correct overloaded function and will always use
the first one. It's a limitation, and one that will probably never be
fixed.

I personally suggest not to use overloaded functions, instead use small
suffixes, for instance like most the constructors in the class Exception.
It makes the source code easier to read and less ambiguous.

Regards Gerold Veith