Path: csiph.com!news.swapon.de!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Steven Simpson Newsgroups: comp.lang.java.programmer Subject: Re: void Date: Sun, 17 Jul 2016 09:21:05 +0100 Organization: A noiseless patient Spider Lines: 17 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: mx02.eternal-september.org; posting-host="dea6e33f83a7656c668e0e6fc8625b50"; logging-data="27914"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18Z3FTX800mNYvzUVlUlIhRedEvWynkAag=" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0 In-Reply-To: Cancel-Lock: sha1:nc9/YvrU9xesak4TI8RvYTM6z4o= Xref: csiph.com comp.lang.java.programmer:34936 On 16/07/16 23:49, Martin Gregorie wrote: > This is unlike C, where a function declared as "void free(void ptr)" > means that free() takes an untyped pointer and returns an untyped pointer > value. Hmm? You mean "void *free(void *)", surely? > BUT note the void as a return value is ambiguous in C because it > can also mean that nothing is returned by a function. There's no ambiguity; a void return type only ever means that nothing is returned. void* is a different type, related to void mnemonically at best. -- ss at comp dot lancs dot ac dot uk