🚀 go-pugleaf

These "unsafe" warnings were introduced because of Delphi .NET.
Borland wants to show which code shouldn't be used anymore if it should stay
protable. .NET still allows pointers but only in "unsafe sections".
The Windows API however requires you sometimes to use pointers, only in
combination with .NET these warnings can really be avoided, using the new
.NET-Api.
You could redeclare the WinAPI call to use var-Parameters.

Something like this (However I don't think this is really nice nor usefull):

Declaration:
========
function GetDiskFreeSpaceEx(var Directory: Char; var FreeAvailable,
    TotalSpace: TLargeInteger; var TotalFree: TLargeInteger): Bool; stdcall;

calling the function:
============
var
  a, b, c: Int64;
  s: string;
begin
  s := 'C:\';
  GetDiskFreeSpaceEx(s[1], a, b, c);
   ...
end;

Cheers, Ma�l

"Paul Kumagai" <okumaware@hotmail.com> schrieb im Newsbeitrag
news:3ffbb2a3@newsgroups.borland.com...
> How do you get around the compiler warnings about unsafe type and unsafe
> code.
>
> I know that I can just turn off the warnings, but is there another way to
> make the the following call?
>
> GetDiskFreeSpaceEx(PChar(DriveLetter),
> FreeBytesAvaibleToCaller,TotalNumberOfBytes, @TotalNumberOfFreeBytes);
>
> This line of code get the following warnings
>
> unsafe type 'PChar'
>
> unsafe code '@ operator'
>
> TIA
>
> Paul Kumagai
>
>