From b356f3e43e360a409cd30fac97a0902d9b7ef11f Mon Sep 17 00:00:00 2001 From: Simo Sorce Date: Sun, 14 Dec 2003 12:04:55 +0000 Subject: reduce double explanation of FIXED ARRAYS (This used to be commit 6f33109b102d41d98ffd536fe2234fbaae85b02e) --- source4/build/pidl/NOTES.txt | 17 ++++------------- 1 file changed, 4 insertions(+), 13 deletions(-) (limited to 'source4') diff --git a/source4/build/pidl/NOTES.txt b/source4/build/pidl/NOTES.txt index 6210281244..09bf1e1fa8 100644 --- a/source4/build/pidl/NOTES.txt +++ b/source4/build/pidl/NOTES.txt @@ -12,18 +12,7 @@ both platforms. #define HYPER_T hyper -FIXED ARRAY ------------ - -A fixed array looks like this: - - typedef struct { - long s[4]; - } Struct1; - -the NDR representation looks just like 4 separate long -declarations. The array size is not encoded on the wire. - +Let's look at the mutliple ways you can encode an array. CONFORMANT ARRAYS ----------------- @@ -101,7 +90,9 @@ A fixed array looks like this: long s[10]; } Struct1; -It appears on the wire with no array length. +The NDR representation looks just like 4 separate long +declarations. The array size is not encoded on the wire. + pidl also supports "inline" arrays, which are not part of the IDL/NDR standard. These are declared like this: -- cgit