Path: csiph.com!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: size_t vs long. Date: Mon, 21 Nov 2022 08:51:02 -0800 Organization: None to speak of Lines: 19 Message-ID: <87a64kl095.fsf@nosuchdomain.example.com> References: <5a71fdad-b7d6-4b4a-a3ee-c5a9beb75d28n@googlegroups.com> <20221117011851.690@kylheku.com> <02eee7cc-6d03-420f-adf6-d7b87592fe38n@googlegroups.com> <2b19488a-2675-4dfd-9de8-11720bb222a7n@googlegroups.com> MIME-Version: 1.0 Content-Type: text/plain Injection-Info: reader01.eternal-september.org; posting-host="7e376da9156e73136a4057d08a300317"; logging-data="4038942"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/WgX/MmdokIXkGPk5lAaGi" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) Cancel-Lock: sha1:4aPoCUS9gOAItIHYzQWNxn8jCaM= sha1:IExaHh5wdFp3IF5AU6ogOoKKfLY= Xref: csiph.com comp.lang.c:168325 David Brown writes: [...] > I don't know what time size_t and malloc became de facto standard in C > prior to the first ANSI standard, but I think it would have been long > before glibc was started. (I presume it was before the first edition > of The C Programming Language in 1978.) K&R1 doesn't mention size_t or malloc. It does have a sample implementation of a memory allocator called "alloc" (presented as an example, not as part of the standard library). It returns an unsigned result; unsigned long didn't exist yet. It does mention calloc() as part of the standard library. -- Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com Working, but not speaking, for XCOM Labs void Void(void) { Void(); } /* The recursive call of the void */