From: skaller <skaller@users.sourceforge.net>
To: Jon Harrop <jon@ffconsultancy.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Having '<<', why to use '|>' ?
Date: Wed, 19 Sep 2007 06:41:28 +1000 [thread overview]
Message-ID: <1190148088.6459.75.camel@rosella.wigram> (raw)
In-Reply-To: <200709181742.27747.jon@ffconsultancy.com>
On Tue, 2007-09-18 at 17:42 +0100, Jon Harrop wrote:
> If an OCaml front-end handled unicode with appropriate symbol settings then
> you could use an "o" symbol to mean that infix operator. I think that is a
> good solution, provided you use an editor that supports suitable unicode and
> there is an easy way to enter such things.
Actually no, I tried this. I used gvim and ignored the difficulty
of entering the Unicode characters I wanted.
The problem I found was that the fonts were such that the
character was almost unreadable. And I think i tried,
for example, the high school division sign..
If you tried that with a 'small o' it would just look like a
small 'o' and not the composition operator.
I think this problem might be fixed with lexical coloring though!
--
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net
next prev parent reply other threads:[~2007-09-18 20:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-17 14:36 Fabrice Marchant
2007-09-17 18:59 ` [Caml-list] " Eric Cooper
2007-09-17 19:45 ` Fabrice Marchant
2007-09-17 22:24 ` Julien Moutinho
2007-09-18 5:39 ` Fabrice Marchant
2007-09-18 8:53 ` Julien Moutinho
2007-09-18 9:09 ` Julien Moutinho
2007-09-18 14:12 ` Fabrice Marchant
2007-09-18 16:42 ` Jon Harrop
2007-09-18 20:41 ` skaller [this message]
2007-09-19 19:49 ` Fabrice Marchant
2007-09-19 21:56 ` Vincent Aravantinos
2007-09-20 13:42 ` Ashish Agarwal
2007-09-20 18:37 ` Gabriel Kerneis
2007-09-21 20:58 ` Harrison, John R
2007-09-21 21:44 ` Karl Zilles
2007-09-20 14:39 Aaron Bohannon
2007-09-22 15:22 ` Nicolas Pouillard
2007-09-22 15:43 ` Daniel Bünzli
2007-09-22 23:55 ` Christian Stork
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=1190148088.6459.75.camel@rosella.wigram \
--to=skaller@users.sourceforge.net \
--cc=caml-list@yquem.inria.fr \
--cc=jon@ffconsultancy.com \
/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