From: Jesper Harder <harder@ifa.au.dk>
Cc: tak@kmc.gr.jp
Subject: Re: ELisp-based uncompface
Date: Thu, 12 Feb 2004 06:53:57 +0100 [thread overview]
Message-ID: <m3isicu9l6.fsf@defun.localdomain> (raw)
In-Reply-To: <b9yoes5nd0z.fsf@jpl.org> (Katsumi Yamaoka's message of "Thu, 12 Feb 2004 13:21:32 +0900")
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> It's fast enough for me too, however I heard it takes seconds
> per image in the slow machine.
It takes around 0.3 s (versus 0.03 s for the external decoder) on my
233 MHz pentium box, which I think is a rather low-end machine by
today's standards.
It's not used in a loop, so don't think many will notice any
difference even on a slow machine.
next prev parent reply other threads:[~2004-02-12 5:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 0:46 Katsumi Yamaoka
2004-02-12 3:19 ` Jesper Harder
2004-02-12 4:21 ` Katsumi Yamaoka
2004-02-12 5:53 ` Jesper Harder [this message]
2004-02-12 6:05 ` Katsumi Yamaoka
2004-02-16 14:04 ` Reiner Steib
2004-02-17 5:59 ` Katsumi Yamaoka
2004-02-18 15:47 ` Reiner Steib
2004-02-18 17:23 ` Ted Zlatanov
2004-02-18 23:00 ` Katsumi Yamaoka
2004-02-13 16:25 ` Xavier Maillard
2004-10-11 23:19 ` Katsumi Yamaoka
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=m3isicu9l6.fsf@defun.localdomain \
--to=harder@ifa.au.dk \
--cc=tak@kmc.gr.jp \
/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).