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=-0.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 15320 invoked from network); 9 Jul 2021 19:50:53 -0000 Received: from 1ess.inri.net (216.126.196.35) by inbox.vuxu.org with ESMTPUTF8; 9 Jul 2021 19:50:52 -0000 Received: from mail-pj1-f43.google.com ([209.85.216.43]) by 1ess; Fri Jul 9 15:43:14 -0400 2021 Received: by mail-pj1-f43.google.com with SMTP id cs1-20020a17090af501b0290170856e1a8aso8830008pjb.3 for <9front@9front.org>; Fri, 09 Jul 2021 12:43:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=nqbCQkO2LdaLj1leEn2e+Hsr9fTLxrfRiulRpwQx8mo=; b=KZqPz1XoOKljHYuAjl5eyjE0yo1H6Xn3MVGAfBCne76GFos66N7QJ6W6HShdVvASJX aFefMPeC47tyQ+mKKw2cKWAJaJ0TrloNl6bh5MOKspMFhWwQdMaGJfN3WyXA5vR3983N Kvz0bRsbTSuICThXAZ4n23WWONQxAVTQK7YhOCv03QR2COmKuO+ePV3k5h3dr3LRgBbh oj5/3HEiamGfN8s3FcYaSGAw6BuMl9M93FoZZfhF7xli8TDaHB5+k4/dtx0yhufG+ot0 B/TBCdl96EQdsmxzs58RHcB6IIdA1Q9ze0AvdY1lCbNtIC35Y5plOJNUsNstdHngN4SY 7mkw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=nqbCQkO2LdaLj1leEn2e+Hsr9fTLxrfRiulRpwQx8mo=; b=nBIHBbkQQ+PbtyoRoXlGdgyZWsf1KmDB6zuqoE0sP53Ajq/6gKMqTE9530JqTP8au5 MHywwxE3hC8W9G0o9VOyFgit+iCkZKZKVdjavoYMYsTm4pgHUpOGdZvvyHJ4LZFhcjHy LF28JHWkoqqJqCwDvtEas0QO0/nLbb2OzF2IhJg84do6sLS1tnK7BIj+btir9nhNiF9D XEr9cxhbT4B5K+fVZoEKtYxlDThhXjip97L1w/J19GU61F955nr5MWsFJMEsO/AdCGoM Tmu4Zq121YN4T8iW0MNyDe7rPbLXYC1iewtJ50hRVNOpXtD7uQ2UPcyXVbj7SNrYLBID mAKQ== X-Gm-Message-State: AOAM531MC8KvDzE/R9Nl92Q/NEMJHQTVeKcO4luqMejH95dS9s6IVNZr LNZcBqFAzh1f1gMAAjdiezLXWE6t9K88ko2HPSVFmOlJ X-Google-Smtp-Source: ABdhPJzYEOl7eK9eso7/VTGY2BsqTyPLIaWwrV4aAwQBJKlLTluXm3ahaD8S8CVfRo7R0rAGXhL1y3fjwhwVPjb2jtY= X-Received: by 2002:a17:90b:224a:: with SMTP id hk10mr4200370pjb.235.1625859787722; Fri, 09 Jul 2021 12:43:07 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a05:6a20:a002:b029:1e:dcb9:6f96 with HTTP; Fri, 9 Jul 2021 12:43:07 -0700 (PDT) In-Reply-To: <4754C6E8-2D26-46FC-B1EB-44AECD8DC0B5@stanleylieber.com> References: <270BEC567655102DE0C764820FA16F74@eigenstate.org> <4754C6E8-2D26-46FC-B1EB-44AECD8DC0B5@stanleylieber.com> From: hiro <23hiro@gmail.com> Date: Fri, 9 Jul 2021 21:43:07 +0200 Message-ID: To: 9front@9front.org Content-Type: text/plain; charset="UTF-8" List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: dependency API shader database Subject: Re: [9front] Re: commit 2f8a59f4b5bfe028c022855acc19666d69eed909 Reply-To: 9front@9front.org Precedence: bulk the examples are all weird. i still do not understand what this allows you to do. On 7/9/21, Stanley Lieber wrote: > On July 9, 2021 11:01:19 AM EDT, ori@eigenstate.org wrote: >>Quoth Stanley Lieber : >>> On July 9, 2021 3:48:39 AM EDT, Anthony Martin wrote: >>> >> rc: add subshell-function syntax >>> >> >>> >> fn foo @{bar} is now equivalent to >>> >> fn foo {@{bar}}. As a side effect, >>> >> this disallows creating functions >>> >> named after keywords without first >>> >> quoting them. >>> > >>> >Respectfully, this is just wrong. @ is a >>> >unary operator. Repurposing it to define >>> >a new special kind of function is a bit >>> >much. >>> > >>> >What does this buy you over being explicit >>> >at the call site? >>> > >>> > fn foo { bar } >>> > >>> > @foo >>> > >>> >One color of function is enough. 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. But is it worth the backwards >>> >incompatibility? >>> > >>> >Thanks, >>> > Anthony >>> > >>> >>> if we're introducing breaking changes to important programs like the >>> shell, 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.) >> >>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. >> >> > > thanks. changes to rc are tricky since of all things we expect it to behave > consistently from day to day. I do think I misunderstood the change itself. > 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 truncated. > > sl >