From: "Krishnaswami, Neel" <neelk@cswcasa.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] function vs. parser
Date: Thu, 13 Sep 2001 17:49:44 -0400 [thread overview]
Message-ID: <B1E4D3274D57D411BE8400D0B783FF322E8700@exchange1.cswv.com> (raw)
Brian Rogoff [mailto:bpr@best.com] wrote:
> On Thu, 13 Sep 2001, Krishnaswami, Neel wrote:
> >
> > Yeah, it's a convention, since types are first-class values
> > in Dylan. Such conventions are easy to create in Dylan because
> > it's way permissive about which characters are legal in identifiers
> > than most languages are -- almost all punctuation is legal. This
> > produces a different set of complaints, though: people are unhappy
> > that they have to write "foo + bar", because "foo+bar" is a distinct
> > identifier.
>
> This is a good thing IMO. The only exceptions of course being
> things like (), ;, and ",".
I agree with you, but the sheer volume is astounding. If I were a
language designer, I'd strongly consider restricting identifiers to
[a-zA-Z0-9_] just to keep the noise level down! It sucks, but in a
traditional way. :)
> > > Maybe in a post-Unicode world everything will be OK.
>
> I guess I really should have put a :-) there, huh?
Probably -- I've seen too many people seriously propose this to read
it as a joke anymore.
> > Doesn't Caml use such a convention to set the precedence of infix
> > functions, so that *.. has higher precedence that +..?
>
> Yes, be careful with | vs || and stuff like that with infixes. I got
> burned there recently. Doh!
Ooh, that's nasty.
> > I think that's pretty neat actually. I find it much more readable
> > than Haskell's `backquote` mechanism.
>
> But you can use names with backquotes.
That's -why- I find it more readable. Simple juxtaposition is usually
left-to-right function application, with the exception that things made
of nonalphabetic characters are infix. Seeing something like x `frob` y
is really hard for me to read, since I want to read it as the function
x taking two arguments. But maybe this just takes a little more practice
than I've had.
Anyway, for some Caml-related content, is there a way to use qualified
paths and infix notation together?
I mean, if I have:
module Foo = struct let (+++) x y = List.append x y end
Right now I have to write
Foo.(+++) [1; 2] [3; 4]
Is there any way I can write something like
[1; 2] Foo.+++ [3; 4]
without using open or rebinding the Foo module's function in the local
namespace?
--
Neel Krishnaswami
neelk@cswcasa.com
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next reply other threads:[~2001-09-13 21:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-13 21:49 Krishnaswami, Neel [this message]
2001-09-14 12:50 ` Gerd Stolpmann
-- strict thread matches above, loose matches on Subject: below --
2001-09-13 18:09 Krishnaswami, Neel
2001-09-13 20:55 ` Brian Rogoff
2001-09-13 8:20 SooHyoung Oh
2001-09-13 8:48 ` Daniel de Rauglaudre
2001-09-13 14:13 ` Brian Rogoff
2001-09-13 16:09 ` Daniel de Rauglaudre
2001-09-13 16:50 ` Brian Rogoff
2001-09-13 16:51 ` Pierre Weis
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=B1E4D3274D57D411BE8400D0B783FF322E8700@exchange1.cswv.com \
--to=neelk@cswcasa.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).