From: Harry Kalogirou <harkal@gmx.net>
To: David Given <dg@cowlark.com>
Cc: Linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: binary size changes from 0.1.0
Date: Fri, 11 Jun 2004 03:52:23 +0300 [thread overview]
Message-ID: <1086904319.1095.417.camel@cool> (raw)
In-Reply-To: <200406101052.50052.dg@cowlark.com>
> One common trick is to not keep the list of error messages in memory at all,
> but to keep them in a file on disk. When perror() is called, the file is
> opened, read until the right error message is found, and that one used...
I think ELKS's libc does that... at least it used to do...
--
Harry Kalogirou <harkal@gmx.net>
next prev parent reply other threads:[~2004-06-11 0:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 18:55 binary size changes from 0.1.0 claudio
2004-06-10 7:35 ` Gábor Lénárt
2004-06-10 9:52 ` David Given
2004-06-10 11:05 ` Gábor Lénárt
2004-06-11 0:52 ` Harry Kalogirou [this message]
2004-06-11 14:36 ` claudio
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=1086904319.1095.417.camel@cool \
--to=harkal@gmx.net \
--cc=dg@cowlark.com \
--cc=linux-8086@vger.kernel.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