caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Yaron M. Minsky" <yminsky@cs.cornell.edu>
To: Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] hash objectified
Date: 25 Aug 2003 21:40:59 -0400	[thread overview]
Message-ID: <1061862059.15526.15.camel@dragonfly.localdomain> (raw)
In-Reply-To: <20030825173217.GA24098@cs.brown.edu>

My take on the same problem was to define infix notation for a few
oft-used operations, including some hash table operations.  To that end
I defined

   h |> k

to lookup key k in hashtable h, and 

   h |< (k,d)

to add the key,data pair (k,d) to h.  It has the downside of obscurity
to the uninitiated, but I find it a lot easier to read code that uses
these operators than the rather overlong Hashtbl.* equivalents.

y

On Mon, 2003-08-25 at 13:32, Manos Renieris wrote:
> On Mon, Aug 25, 2003 at 05:46:39PM +0200, KONTRA Gergely wrote:
> > 
> > Hashtbl.add h "foo" "bar" <--> h#add "foo" "bar"
> > 
> > Because it is shorter to type -> less errors, quicker programming
> > OO can be cool. (see ruby)
> > I'm not OO fan, but lazy :)
> 
> If that's the reason, once you do
>     module H = Hashtbl
> then
>     H.add h "foo" "bar"
> is only two characters longer, and one shift shorter :-)
> And the compiler ensures the exact type of h, and you know statically
> what function you call -> less to keep in your head -> less errors,
> quicker programming.
> 
> -- Manos
> 
> -------------------
> To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
> Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
-- 
|--------/            Yaron M. Minsky              \--------|
|--------\ http://www.cs.cornell.edu/home/yminsky/ /--------|

Open PGP --- KeyID B1FFD916 (new key as of Dec 4th)
Fingerprint: 5BF6 83E1 0CE3 1043 95D8 F8D5 9F12 B3A9 B1FF D916



-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


      parent reply	other threads:[~2003-08-26  1:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-12 19:31 KONTRA Gergely
2003-08-18 12:50 ` Xavier Leroy
2003-08-18 14:40   ` William Lovas
2003-08-18 15:09     ` Xavier Leroy
2003-08-18 15:57       ` William Lovas
2003-08-21 10:24     ` KONTRA Gergely
2003-08-21 16:58       ` William Lovas
2003-08-25 15:46         ` KONTRA Gergely
2003-08-25 17:32           ` Manos Renieris
2003-08-25 18:13             ` henridf
2003-08-26  1:40             ` Yaron M. Minsky [this message]

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=1061862059.15526.15.camel@dragonfly.localdomain \
    --to=yminsky@cs.cornell.edu \
    --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).