Discussion about C array type semantics
The article discusses the peculiarities of C array types and their semantics. It highlights how array types are treated as pointers in many contexts, which can lead to confusion. The author suggests that a clearer distinction between arrays and pointers could simplify understanding for learners.
- ▪In C, an array type T[n] is distinct from a pointer type T *, but expressions of type T[n] convert to a pointer to the first element.
- ▪The sizeof operator behaves differently for arrays and pointers, leading to potential discrepancies in size calculations.
- ▪Function signatures interpret array types as pointers, discarding the size information, which complicates their usage.
Lobsters files mainly under programming. We currently carry 187 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Anselmschueler |
| Canonical URL | https://anselmschueler.com/blogposts/2025-c-pointers/ |
| Publication time | Sun, 24 May 2026 17:57:46 -0500 |
| Retrieval time | 2026-05-24T23:07:34.930Z |
| Last seen | 2026-05-24T23:07:34.930Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | -74V1vI9bNdf |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
C array types are weird In this article I’ll explain what I find weird about them, what I’d do differently, and ramble on a few related things. Technically speaking, an array type T[n] (for some n) is distinct from a pointer type T *. A value of type T[n] represents a contiguous sequence of T values in memory, n long. But you can’t actually refer to values of type T[n]. Any expression that would be of that type is immediately converted to a pointer, type T *, namely a pointer to the first element. Since the array indexing operator arr[ix] actually operates on pointers, acting like *(arr + ix), you can basically treat arrays like pointers. An important instance where this doesn’t happen is in sizeof arr, which returns sizeof(T) × n.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Anselmschueler.
Discussion
0 commentsMore from Anselmschueler
