From: "Yann Régis-Gianas" <yann.regis-gianas@inria.fr>
To: "Robert Fischer" <Robert@fischerventure.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Should a /\ operator be possible?
Date: Fri, 2 May 2008 19:02:46 +0200 [thread overview]
Message-ID: <1af89fca0805021002j26c78214m84b4a7adafb38ef@mail.gmail.com> (raw)
In-Reply-To: <481B24DB.5030709@FischerVenture.com>
Note that emacs22 has a TeX input mode which enables you to write TeX
commands instead of tedious numeric code. I use it for my Coq
development, \forall in the emacs buffer is translated to the
corresponding unicode symbol on-the-fly.
On Fri, May 2, 2008 at 4:27 PM, Robert Fischer
<Robert@fischerventure.com> wrote:
> Yeah, I vote against having to type Alt+number to edit someone else's
> code. I'd rather that we start allowing LaTeX symbols in our source
> before we actually have the Unicode symbols themselves in there.
>
> Oh, and +1 for actually supporting Unicode in String processing.
>
> ~~ Robert.
>
>
>
> Alain Frisch wrote:
> > Richard Jones wrote:
> >> In fact can we open the discussion about converting OCaml source files
> >> into UTF-8 and allow _lots_ more symbols? eg:
> >>
> >> let (∪) = ...
> >> let (⊆) = ...
> >
> > Shouldn't this desire of using mathematical symbols be addressed at
> > the level of your editor / IDE instead? If the language allowed you
> > to define and use alphanumeric infix operators like:
> >
> > let (`subseteq`) = ...
> > if (x `subseteq` y) then ...
> >
> > then you could simply inform your editor that it should display
> > `subseteq` as ⊆. The tuareg mode already does this kind of
> > "symbolification" of some operators like -> (displayed as an arrow)
> > and 'a (display as a Greek alpha) and it shouldn't be too difficult to
> > extend that to user-defined operators.
> >
> > -- Alain
> >
> > _______________________________________________
> > Caml-list mailing list. Subscription management:
> > http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> > Archives: http://caml.inria.fr
> > Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> > Bug reports: http://caml.inria.fr/bin/caml-bugs
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
--
Yann Régis-Gianas
next prev parent reply other threads:[~2008-05-02 17:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-01 19:41 Richard Jones
2008-05-01 21:20 ` [Caml-list] " Richard Jones
2008-05-01 21:36 ` Hezekiah M. Carty
2008-05-02 7:44 ` Gordon Henriksen
2008-05-02 6:43 ` Vincent Hanquez
2008-05-02 8:05 ` David Teller
2008-05-02 8:26 ` Richard Jones
2008-05-02 9:23 ` Alain Frisch
2008-05-02 11:54 ` Daniel Bünzli
2008-05-05 6:36 ` Maxence Guesdon
2008-05-02 14:27 ` Robert Fischer
2008-05-02 17:02 ` Yann Régis-Gianas [this message]
2008-05-02 15:11 ` Hezekiah M. Carty
2008-05-02 15:25 ` Alain Frisch
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1af89fca0805021002j26c78214m84b4a7adafb38ef@mail.gmail.com \
--to=yann.regis-gianas@inria.fr \
--cc=Robert@fischerventure.com \
--cc=caml-list@inria.fr \
/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 NNTP newsgroup(s).