From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: [External] : Passing buffers to function in elisp
Date: Sat, 25 Feb 2023 12:23:22 +0100 [thread overview]
Message-ID: <87pm9yf0ph.fsf@web.de> (raw)
In-Reply-To: 87bklihln8.fsf@iki.fi
Petteri Hintsanen <petterih@iki.fi> writes:
> (defun emms-info-native--read-and-decode-ogg-page (filename offset)
> (with-temp-buffer
> (set-buffer-multibyte nil)
> (insert-file-contents-literally filename
> nil
> offset
> (+ offset
> emms-info-native--ogg-page-size))
> (emms-info-native--decode-ogg-page (buffer-string))))
> [...]
>
> (defun emms-info-native--decode-ogg-packets (filename packets)
> (let ((num-packets 0)
> (offset 0)
> (stream (vector)))
> (while (< num-packets packets)
> (let ((page (emms-info-native--read-and-decode-ogg-page filename
> offset)))
> (cl-incf num-packets (or (plist-get page :num-packets) 0))
> (cl-incf offset (plist-get page :num-bytes))
> (setq stream (vconcat stream (plist-get page :stream)))
> stream))
If `emms-info-native--read-and-decode-ogg-page' is called very often
(hundreds of times or more), it's probably better to use one single
buffer instead of a fresh temp buffer every single time. Using temp
buffers creates quite a bunch of garbage IME.
Michael.
next prev parent reply other threads:[~2023-02-25 11:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 21:18 Passing buffers to function in elisp Petteri Hintsanen
2023-02-21 23:21 ` [External] : " Drew Adams
2023-02-22 5:35 ` tomas
2023-02-24 20:08 ` Petteri Hintsanen
2023-02-25 6:40 ` tomas
2023-02-25 11:23 ` Michael Heerdegen [this message]
2023-02-25 13:45 ` tomas
2023-02-25 18:31 ` Michael Heerdegen
2023-02-25 19:05 ` tomas
2023-02-25 23:52 ` Stefan Monnier via Users list for the GNU Emacs text editor
2023-02-27 20:44 ` Petteri Hintsanen
2023-02-28 5:37 ` tomas
2023-03-03 15:19 ` Stefan Monnier via Users list for the GNU Emacs text editor
2023-03-07 21:48 ` Petteri Hintsanen
2023-03-07 22:45 ` Stefan Monnier
2023-03-08 5:38 ` tomas
2023-09-06 19:05 ` Petteri Hintsanen
2023-09-06 21:12 ` Stefan Monnier
2023-02-22 5:30 ` tomas
2023-02-23 9:34 ` Michael Heerdegen
2023-02-23 9:51 ` tomas
2023-02-23 16:19 ` Marcin Borkowski
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=87pm9yf0ph.fsf@web.de \
--to=michael_heerdegen@web.de \
--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).