From: dmr@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] thread
Date: Fri, 6 Jul 2001 01:55:09 -0400 [thread overview]
Message-ID: <20010706055512.42D78199D7@mail.cse.psu.edu> (raw)
So far as I can determine, the Plan 9 C compiler is
conformant here.
If you have, say, an
int A[10];
then just A is the address of A and has type int *.
&A is a pointer to this array of 10 integers; it will
have the same value, as a pointer, but a different type:
int (*)[10]
The reason why the initialization in the thread man page,
(and presumably the code) works is that the thing being
assigned to is void *, and any object pointer will fit; the
coercion just happens.
The & in &m is redundant, probably misleading, but ultimately
harmless. Kenji's example with print likewise has the
same character, since print is a variadic function, and all
his second arguments fall under the ... in its declaration,
and so aren't type-checked.
Incidentally, there is no C-language guarantee that the
actual bit pattern produced by A and &A will be identical,
though in practice they usually will be for most compilers,
yet they still have different types.
For a case in which the type-checking is more evident, without
the laxness of void * or ..., try compiling
#include <u.h>
#include <libc.h>
void t1(int *ip);
void t2(int (*iap)[10]);
void
main(void)
{
int ia[10];
t1(ia);
t1(&ia);
t2(ia);
t2(&ia);
}
You will get errors on lines 13 [ t1(&ia) ] and
14 [ t2(ia) ].
Dennis
next reply other threads:[~2001-07-06 5:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-06 5:55 dmr [this message]
2001-07-06 16:54 ` Digby Tarvin
2001-07-09 8:33 ` Douglas A. Gwyn
2001-07-09 11:46 ` Digby Tarvin
2001-07-09 17:03 ` Dan Cross
2001-07-09 11:49 ` Boyd Roberts
-- strict thread matches above, loose matches on Subject: below --
2001-07-06 4:15 arisawa
2001-07-06 14:41 ` Dan Cross
2001-07-06 18:24 ` Boyd Roberts
2001-07-06 1:02 rob pike
2001-07-06 0:50 arisawa
2001-07-06 2:05 ` Dan Cross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010706055512.42D78199D7@mail.cse.psu.edu \
--to=dmr@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).