Path: ...!weretis.net!feeder8.news.weretis.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: bart Newsgroups: comp.lang.c Subject: Re: Writing own source disk Date: Mon, 3 Jun 2024 00:10:15 +0100 Organization: A noiseless patient Spider Lines: 15 Message-ID: References: <87sexvm1lr.fsf@bsb.me.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Mon, 03 Jun 2024 01:10:15 +0200 (CEST) Injection-Info: dont-email.me; posting-host="d2cae1aa4235874fd2214b538c145732"; logging-data="3741703"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19YiW95zpSxj2W40EX6Cn/j" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:SFDz4uigJaSBf334oj/untM+5EI= In-Reply-To: <87sexvm1lr.fsf@bsb.me.uk> Content-Language: en-GB Bytes: 1554 On 02/06/2024 23:17, Ben Bacarisse wrote: > Malcolm McLean writes: > >> Writing a prgram which writes its own source to standard output is a >> standard programming problem. It's called a quine. > > A quine must also not process any input. No input at compile-time or runtime? A compiler necessarily has to have the source code of the program as input, so what are the limitations? A C program can use #include; does that extend to directives like #embed, or is that considered cheating?