| Deutsch English Français Italiano |
|
<vcb4il$234i0$1@news.xmission.com> View for Bookmarking (what is this?) Look up another Usenet article |
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: Another 'What's the diff Q" (LDo will like this) Date: Tue, 17 Sep 2024 05:37:25 -0000 (UTC) Organization: The official candy of the new Millennium Message-ID: <vcb4il$234i0$1@news.xmission.com> Injection-Date: Tue, 17 Sep 2024 05:37:25 -0000 (UTC) Injection-Info: news.xmission.com; posting-host="shell.xmission.com:166.70.8.4"; logging-data="2200128"; mail-complaints-to="abuse@xmission.com" X-Newsreader: trn 4.0-test77 (Sep 1, 2010) Originator: gazelle@shell.xmission.com (Kenny McCormack) Bytes: 1323 Lines: 26 (bash) What is the difference between << and <<<, from a functionality POV? I.e., is there anything you can do with one but not the other? I'm talking about this: $ cmd << 'EOF' .... .... EOF $ vs. $ cmd <<< ' .... .... ' $ Of course I know, as does everybody, that << is legacy and <<< is new, but it begs the question: Why was <<< added to the language? Note that I use both constructs, as the mood suits me, but I just got to thinking that maybe <<< doesn't actually add any new functionality. -- Adderall, pseudoephed, teleprompter