From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: * X-Spam-Status: No, score=1.1 required=5.0 tests=DATE_IN_PAST_06_12 autolearn=no autolearn_force=no version=3.4.4 Received: (qmail 26344 invoked from network); 10 Jul 2021 02:22:10 -0000 Received: from 1ess.inri.net (216.126.196.35) by inbox.vuxu.org with ESMTPUTF8; 10 Jul 2021 02:22:10 -0000 Received: from 5ess.inri.net ([107.191.111.177]) by 1ess; Fri Jul 9 11:30:02 -0400 2021 Received: from [127.0.0.1] ([104.59.85.219]) by 5ess; Fri Jul 9 11:10:07 -0400 2021 Date: Fri, 09 Jul 2021 11:10:05 -0400 From: Stanley Lieber To: 9front@9front.org In-Reply-To: <270BEC567655102DE0C764820FA16F74@eigenstate.org> References: <270BEC567655102DE0C764820FA16F74@eigenstate.org> Message-ID: <4754C6E8-2D26-46FC-B1EB-44AECD8DC0B5@stanleylieber.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: realtime-java event service DOM database Subject: Re: [9front] Re: commit 2f8a59f4b5bfe028c022855acc19666d69eed909 Reply-To: 9front@9front.org Precedence: bulk On July 9, 2021 11:01:19 AM EDT, ori@eigenstate=2Eorg wrote: >Quoth Stanley Lieber : >> On July 9, 2021 3:48:39 AM EDT, Anthony Martin wro= te: >> >> rc: add subshell-function syntax >> >> >> >> fn foo @{bar} is now equivalent to >> >> fn foo {@{bar}}=2E As a side effect, >> >> this disallows creating functions >> >> named after keywords without first >> >> quoting them=2E >> > >> >Respectfully, this is just wrong=2E @ is a >> >unary operator=2E Repurposing it to define >> >a new special kind of function is a bit >> >much=2E >> > >> >What does this buy you over being explicit >> >at the call site? >> > >> > fn foo { bar } >> > >> > @foo >> > >> >One color of function is enough=2E What's >> >next? >> > >> > fn foo !{ bar } >> > >> >to mean that foo always negates the exit >> >status of its body? >> > >> >The new quoting requirement for functions >> >named after keywords seems fine, on the >> >other hand=2E But is it worth the backwards >> >incompatibility? >> > >> >Thanks, >> > Anthony >> > >>=20 >> if we're introducing breaking changes to important programs like the sh= ell, can we please at least post a warning on the mailing list? > >(caveat -- it's compatible unless you >happen to be using functions named '@', >'`', etc -- which, again, you >can't use without quoting=2E) > >I don't think most people even realize >that it's possible to name an rc function: > > '@{this is a valid} function name!' > >Either way, noted -- I'll post next time=2E > > thanks=2E changes to rc are tricky since of all things we expect it to beh= ave consistently from day to day=2E I do think I misunderstood the change i= tself=2E I've been running sysupdate from cron and piping the output to an = e-mail to myself -- the commit messages as printed by sysupdate are truncat= ed=2E sl