unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Arne Babenhauserheide <arne_bab@web.de>
To: guile-devel@gnu.org
Cc: Tirifto <tirifto@posteo.cz>
Subject: Re: Unicode procedure names
Date: Tue, 16 Jul 2019 01:52:39 +0200	[thread overview]
Message-ID: <8736j6g8jc.fsf@web.de> (raw)
In-Reply-To: <87y30zgfuc.fsf@elephly.net>

[-- Attachment #1: Type: text/plain, Size: 1107 bytes --]


Ricardo Wurmus <rekado@elephly.net> writes:

> Tirifto <tirifto@posteo.cz> writes:
>
>> I was recently looking into Perl 6 and noticed a very neat feature
>> about it: Unicode operators! That is, it makes use of some Unicode
>> symbols to offer alternatives to awkward or verbose ASCII notation.
>> For instance, ‘>=’ and ‘<=’ may just as well be written as ‘≥’ and
>> ‘≤’, respectively. [1] And ‘∈’ checks whether an item is an element
>> of a list. [2] [3]
>
> Neat.
>
>> Now, I don't know if this is something you think would be nice to have
>> baked into Guile, but I really liked the idea, and thought to share it
>> in the case you would, too (and have't thought of it yet). :)
>
> I think this could be implemented as a library of aliase and thus
> wouldn’t need to have any privileged access to Guile itself.

All you need to do is

(define ≥ >=)

And you can use (≥ 2 1) — if you use SRFI-105 (#!curly-infix), then you
can also use it as {2 ≥ 1}.

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein
ohne es zu merken

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1076 bytes --]

  reply	other threads:[~2019-07-15 23:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-12 15:59 Unicode procedure names Tirifto
2019-07-15 21:14 ` Ricardo Wurmus
2019-07-15 23:52   ` Arne Babenhauserheide [this message]
2019-07-16 12:41     ` Ricardo Wurmus
2019-07-16 12:51       ` Hans Åberg
2019-07-16 13:18         ` Arne Babenhauserheide
2019-07-16 13:49           ` Hans Åberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8736j6g8jc.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=guile-devel@gnu.org \
    --cc=tirifto@posteo.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).