Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Anton Shepelev Newsgroups: comp.lang.c Subject: Re: Word For Today: =?UTF-8?Q?=E2=80=9CUglification=E2=80=9D?= Date: Tue, 12 Mar 2024 18:09:04 +0300 Organization: A noiseless patient Spider Lines: 27 Message-ID: <20240312180904.ac3a5856df424c396689db3e@g{oogle}mail.com> References: <20240312003531.349@kylheku.com> <20240312174600.5b88613545da9f667e06a4c6@g{oogle}mail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Injection-Info: dont-email.me; posting-host="d13e3206328941c7d8e4f3573f34dc72"; logging-data="378183"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/spFp1VH7Pfs1j7be+gJEX7XvXvBXXAnI=" Cancel-Lock: sha1:CEhuMxleT98kD7vI5AP0N0hsR8k= X-Newsreader: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32) Bytes: 2219 bart: > Anton Shepelev: > > David Brown: > > > > > The limited support for avoiding name clashes in C > > > (user-level C, outside of the implementation > > > internals) is certainly something that he (or others) > > > /could/ complain about. It is a well-known issue, and > > > it's a shame that the C standards committee have never > > > dealt with it. I don't see why the language could not > > > adopt a simple "namespace" solution that would hugely > > > simplify avoiding identifier clashes. (It wouldn't > > > help for macros, but we have inline functions to > > > handle many cases.) > > > > My hypothetical solution is to have a single function > > returning a struct with pointers to all the public > > functions of a module. > > What stops that function name clashing with the single > function exported from other people's modules? A much lower probability. -- () ascii ribbon campaign -- against html e-mail /\ www.asciiribbon.org -- against proprietary attachments