procedure TUDPSocket.TNMUDP1DataReceived(Sender: TComponent;
? NumberBytes: Integer; FromIP: String; Port: Integer);
var
? Buffer: array of Char;
?
begin
? SetLength(Buffer,NumberBytes);
? TNMUDP1.ReadBuffer(Buffer, NumberBytes);
end;
?
end.

or:
         TNMUDP1.ReadBuffer(@Buffer[0], NumberBytes);

You might need to use a bit more typecasting

Personally I would make Buffer a String

On Mon, 19 May 2003 13:20:37 GMT, "Ullas" <ul...@linknet.com.au>
wrote:

Thank you.

I am new to Delphi - coming from VB. If I was to make Buffer a
string how would I typecast it so ReadBuffer would see it as an
array of char?

Using :  S[1] is great when a PChar is expected

[Those extra eight bytes, and all those known-zeroes, can avoid a hornet's
nest of nasss-s-s-s--sty problems.]

When you've got a packet, set the array-size and use a <!>ed 'for' loop to
fill it.

Unless you have an /incredible/ amount of traffic coming in every
millisecond, the CPU will be grateful that you gave it something to do, no
matter how trivial it might be.

I always advocate going for the simplest solution, not the cleverest.  If at
some time in the future you slap a performance-probe on the program and
"this particular harbor" (yeah, I was groovin' to Jimmy Buffett last night)
shows up as a cherry-red hot spot, /then/ and /only/ then do you reimplement
it.

The true 'hot spots' in a program are almost never where you expect them to
be.

- I was daft enough to _not_ realize that he is dealing with a 3rd
party component, that utilizes a fixed length (but rigorously checked)
buffer and allows partial fills.

I would also add to your recommendation :-

type
  TCharArray = array[1..10000] of char;
  PCharArray = ^TCharArray;
var
  buffer: PCharArray;
begin
  GetMem(buffer, NumberBytes);
  TNMUDP1.ReadBuffer(buffer^, NumberBytes);
  FreeMem(buffer);
end;

--
Regards