caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: tmp123 <tmp123@menta.net>
To: caml-list <caml-list@yquem.inria.fr>
Subject: next eleemnt in set
Date: Wed, 13 Feb 2008 09:35:50 +0100	[thread overview]
Message-ID: <47B2ABE6.9090605@menta.net> (raw)

Hello,

Thanks for your time.

I'm wondering which abstract type (set, map, ...) is the most useful to 
implement the following 3 methods: given a set of values, that are 
unique and ordered (it exists a "compare" function), it is necessary, in 
addition to the "add" and "remove element" methods, to have a "next" 
method. The next method takes as parameter one element of the set, and 
must return the immediatelly next element of the set, according to the 
provided compare function.

Please, have someone any suggestion?

Thanks again.


             reply	other threads:[~2008-02-13  8:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-13  8:35 tmp123 [this message]
2008-02-13  8:50 ` [Caml-list] " Xavier Leroy
2008-02-14  8:33   ` tmp123

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=47B2ABE6.9090605@menta.net \
    --to=tmp123@menta.net \
    --cc=caml-list@yquem.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).