unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: how to access a large datastructure efficiently?
Date: Thu, 04 Mar 2010 08:25:52 +0100	[thread overview]
Message-ID: <87y6i8r1j3.fsf@tux.homenetwork> (raw)
In-Reply-To: 873a0gshb6.fsf@tux.homenetwork

Thierry Volpiatto <thierry.volpiatto@gmail.com> writes:

> Hi,
>
> Christian Wittern <cwittern@gmail.com> writes:
>
>> Hi there,
>>
>> Here is the problem I am trying to solve:
>>
>> I have a large list of items which I want to access.  The items are in 
>> sequential order, but many are missing in between, like:
>>
>> (1 8 17 23 25 34 45 47 50)  [in reality, there is a value associated 
>> with this, but I took it out for simplicity]
>>
>> Now when I am trying to access with a key that is not in the list, I 
>> want to have the one with the closest smaller key returned, so for 6 
>> and 7 this would be 1, but for 8 and 9 this would be 8.
>>
>> Since the list will have thousands of elements, I do not want to simply 
>> loop through it but am looking for better ways to do this in Emacs lisp.  
>> Any ideas how to achieve this?
>
> ,----
> | (defun closest-elm-in-seq (n seq)
> |   (let ((pair (loop with elm = n with last-elm
> |                  for i in seq
> |                  if (and last-elm (< last-elm elm) (> i elm)) return (list last-elm i)
> |                  do (setq last-elm i))))
> |     (if (< (- n (car pair)) (- (cadr pair) n))
> |         (car pair) (cadr pair))))
> `----
>
> That return the closest, but not the smaller closest, but it should be
> easy to adapt.

Case where your element is member of list, return it:

,----
| (defun closest-elm-in-seq (n seq)
|   (let ((pair (loop with elm = n with last-elm
|                  for i in seq
|                  if (eq i elm) return (list i)
|                  else if (and last-elm (< last-elm elm) (> i elm)) return (list last-elm i)
|                  do (setq last-elm i))))
|     (if (> (length pair) 1)
|         (if (< (- n (car pair)) (- (cadr pair) n))
|             (car pair) (cadr pair))
|         (car pair))))
`----
For the smallest just return the car...

-- 
Thierry Volpiatto
Gpg key: http://pgp.mit.edu/





  reply	other threads:[~2010-03-04  7:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-04  1:50 how to access a large datastructure efficiently? Christian Wittern
2010-03-04  6:59 ` Thierry Volpiatto
2010-03-04  7:25   ` Thierry Volpiatto [this message]
2010-03-04  8:13     ` Andreas Röhler
2010-03-04 11:00       ` Thierry Volpiatto
2010-03-04 15:49         ` Andreas Röhler
2010-03-04 16:09           ` Thierry Volpiatto
2010-03-04  8:15     ` Christian Wittern
2010-03-04 10:24       ` Thierry Volpiatto
2010-03-04 15:01       ` Thien-Thi Nguyen
2010-03-04 16:49       ` Andreas Politz
     [not found] <mailman.2247.1267667449.14305.help-gnu-emacs@gnu.org>
2010-03-04 10:36 ` Alan Mackenzie
2010-03-04 20:22 ` Pascal J. Bourguignon
2010-03-05  0:29 ` Stefan Monnier

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y6i8r1j3.fsf@tux.homenetwork \
    --to=thierry.volpiatto@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).