Path: ...!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Ben Bacarisse Newsgroups: comp.lang.c Subject: Re: on allowing "int a" definition everywhere Date: Wed, 21 Aug 2024 09:19:21 +0100 Organization: A noiseless patient Spider Lines: 16 Message-ID: <87cym2p9ti.fsf@bsb.me.uk> References: MIME-Version: 1.0 Content-Type: text/plain Injection-Date: Wed, 21 Aug 2024 10:19:21 +0200 (CEST) Injection-Info: dont-email.me; posting-host="fbbdc6bc93fc8e09c145618243cc2ab3"; logging-data="3991012"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/hpEe9a2TQxtdLAWNBPQiC6bB53VMboFI=" User-Agent: Gnus/5.13 (Gnus v5.13) Cancel-Lock: sha1:Oh079qHgbXgMAaJLmHES+c6oDpM= sha1:LYAnjwjiylSFFUijEzd0CkVCotY= X-BSB-Auth: 1.0def8da9d884fb66b968.20240821091921BST.87cym2p9ti.fsf@bsb.me.uk Bytes: 1522 Lawrence D'Oliveiro writes: > On Tue, 20 Aug 2024 18:48:17 +0200, fir wrote: > >> got some thought today thet simply probably allowing to define "int a" >> everywhere could be just simply a good c (or other language) design >> decision > > Somehow along the line from BCPL to B to C, one useful feature was lost: > the ability to have a value-returning statement block inside an > expression. It was lost in the BCPL to B transition. -- Ben.