Jump to content

Talk:Struct (C programming language)

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Abdull (talk | contribs) at 09:18, 2 May 2010 (Call by reference or call by value?: new section). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Article or redirect?

From history, this page has been in three rather different states:

Each is reasonable (although the last perhaps less so), but there seems to have been no discussion of the matter. Worse, the Structs page had gotten set as redirecting to Object composition, making the singular and plural of "struct" refer to very different things.

The evolution seems to be that what started out as being about C (programming language) specifically got geared towards C++, and then towards abstract object orientation. Later someone reacted to this and changed the redirect to the more common (but still abstract) interpretation of Record (computer science). 90.230.192.94 (talk) 17:17, 8 May 2009 (UTC)[reply]

This article should observe that struct names are a namespace separate from the main namespace of types and variables, so that one can declare

typedef struct ListNode { int val; struct ListNode *next; } ListNode;

That is, it is not necessary to use different names (ListNode_ and ListNode) for the two C views of wha is essentially the same data type.
All the best, --Jorge Stolfi (talk) 21:57, 15 May 2009 (UTC)[reply]

Type punning

"For example, common Internet protocols rely on the fact that C compilers insert padding between struct fields in predictable ways [...]"

Is this an example of type punning? --Abdull (talk) 22:52, 2 January 2010 (UTC)[reply]

Call by reference or call by value?

In C, when calling a subroutine or receiving a return value, is a struct passed/returned by value or by reference? Does the ISO/IEC C standard discuss this topic explicitly? Thanks, --Abdull (talk) 09:18, 2 May 2010 (UTC)[reply]