Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: usecases of void foo(char **b) {} Date: Sat, 05 Nov 2016 14:12:04 -0700 Organization: None to speak of Lines: 28 Message-ID: References: <5a9aae7f-eb86-4c7b-bc93-142504b1d0a9@googlegroups.com> <53f08403-90c0-4850-9d2a-734c7735cf2e@googlegroups.com> <51ff36ac-0a7f-4d4b-9c7d-5727160bd34e@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: mx02.eternal-september.org; posting-host="068e13fa936d4e49cf562f96621eaf4d"; logging-data="30532"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19v3pGG4yIPkA2RA3/I5U0J" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:PKtDcd2iKfbHDACw6TrRF4Y87tg= sha1:XPohELP7wN8HUnyURKkKgweq0bk= Xref: csiph.com comp.lang.c:95858 "Pascal J. Bourguignon" writes: > David Brown writes: >> Don't allow null pointers. > > This doesn't really make a difference. Yes, it does. > int null=0; > #define NULL (&null) > int* p=NULL; Sure, you can probably reinvent something like a null pointers in a language that doesn't permit them. Languages that don't permit null pointers don't just start with a language that does permit them and then remove that one feature. They're designed to work with pointers that logically cannot be null. I'm not familiar enough with any such languages to discuss them intelligently (even to the point of citing one), but if you're curious you might want to do some research. -- Keith Thompson (The_Other_Keith) kst-u@mib.org Working, but not speaking, for JetHead Development, Inc. "We must do something. This is something. Therefore, we must do this." -- Antony Jay and Jonathan Lynn, "Yes Minister"