Path: ...!weretis.net!feeder9.news.weretis.net!xmission!nnrp.xmission!.POSTED.shell.xmission.com!not-for-mail
From: gazelle@shell.xmission.com (Kenny McCormack)
Newsgroups: comp.unix.shell
Subject: Re: Another 'What's the diff Q" (LDo will like this)
Date: Tue, 17 Sep 2024 20:39:05 -0000 (UTC)
Organization: The official candy of the new Millennium
Message-ID: <vccpd9$23si3$1@news.xmission.com>
References: <vcb4il$234i0$1@news.xmission.com> <vccesq$3kjv7$1@dont-email.me> <vccjf5$23rk4$1@news.xmission.com> <20240917132221.49@kylheku.com>
Injection-Date: Tue, 17 Sep 2024 20:39:05 -0000 (UTC)
Injection-Info: news.xmission.com; posting-host="shell.xmission.com:166.70.8.4";
	logging-data="2224707"; mail-complaints-to="abuse@xmission.com"
X-Newsreader: trn 4.0-test77 (Sep 1, 2010)
Originator: gazelle@shell.xmission.com (Kenny McCormack)
Bytes: 2652
Lines: 33

In article <20240917132221.49@kylheku.com>,
Kaz Kylheku  <643-408-1753@kylheku.com> wrote:
>On 2024-09-17, Kenny McCormack <gazelle@shell.xmission.com> wrote:
>> In article <vccesq$3kjv7$1@dont-email.me>,
>> Janis Papanagnou  <janis_papanagnou+ng@hotmail.com> wrote:
>> ...
>>>> I just thought of something.  Suppose your included text contains both
>>>> single and double quotes.  This will not be an issue with <<, but will
>>>> require extra effort (more than I care to expend!) with <<<.
>>>
>>>That's actually the property I like with here-docs; that you can
>>>write your template-like text inside the shell-program text as it
>>>shall (and will) be seen at the target side, both forms of quotes
>>>inclusive.
>>
>> Right.  The point I was making is that this rates as a superiority of <<
>> over <<< - and answers the question posted in the OP: Is there anything one
>> can do that the other cannot?
>
>Many years ago, I was working on an embedded Linux distro (from
>scratch). For text files installed on the target system, like /etc,
>I had a Makefile-based thing which could preprocess files with several
>preprocessors, based on their suffix. One of the preprocessors was
>shell. For those files, what the Makefile did was dynamically 
>generate a temporary script like this:

Perhaps you misread my post.  Perhaps you misread "superiority" as
"inferiority".  I admit that the two words do look pretty similar.

-- 
The randomly chosen signature file that would have appeared here is more than 4
lines long.  As such, it violates one or more Usenet RFCs.  In order to remain
in compliance with said RFCs, the actual sig can be found at the following URL:
	http://user.xmission.com/~gazelle/Sigs/InsaneParty