Re: Access to array slices?

[sk <sk@noname.com>]

tmoran@acm.org
 > it will usually have "chars **buf" or "Handle *h" where ...

A handy rule of thumb which I hope to remember (I think that
"Handle *h" is largely a MS/Window thing isn't it ?).

david.thompson1@worldnet.att.net
 > Allocation has nothing to do with it; a C routine cannot
 > allocate unless it *returns* a pointer or receives a pointer
 > *to* a pointer (or receives a pointer to or returns a struct
 > *containing* a pointer, but that's much rarer).

I seem to recall that some of the Window C routines allocated
some of the data structures internally and passed a (or updated
a passed in) pointer back to the caller ?

One of my major headaches is "char *" being used instead of
"struct sometype *" and not noticing until things blow up and
I have to look at the man pages.

 > readlink actually *could* have been designed and specified

I only had trouble with "readlink" until I RTFM'd. It looked
like the prototype of something else that I was binding to
but it turns out  the parameters behaved differently after all.

I guess there is no replacement for RTFMing to get the parameters
correct, no fancy and handy Char_Array trickery to save the day :-(

Cheers

-- 
--
-- Merge vertically for real address
--
------------------------------------
-- s n p @ t . o
--  k i e k c c m
------------------------------------