From: Stainless Steel Rat <ratinox@peorth.gweep.net>
Subject: Re: PATCH: pop3.el (pop3-movemail): handle network errors
Date: Wed, 7 Apr 1999 17:10:36 -0400 [thread overview]
Message-ID: <99Apr7.170723edt.13858-3@gateway.intersys.com> (raw)
In-Reply-To: pahe@daimi.au.dk's message of "07 Apr 1999 21:21:40 +0200"
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
* pahe@daimi.au.dk (Peter von der Ahé) on Wed, 07 Apr 1999
| I can not see why pop3 needs to be so bare-bone that it can not handle
| simple network errors.
For the simple reason that pop3 is a library, not a client. Libraries
provide functions, clients provide features like error handling.
pop3-movemail is a reference function, something to give real programmers
an example of how to use the library. I never intended it to be used by
anyone but myself (and it constantly amazes me that so many use it anyway).
I have nothing against anyone writing the World's Greatest POP Client.
Please! if you can write the beast then do so. But please, do not expect
me to maintain it. I am not a programmer. Things like condition-case and
throw/catch give me a headache. If I understood them better, I probably
would have included something like that at the outset. I don't. I didn't.
Deal.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v0.9.5 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE3C8nMgl+vIlSVSNkRAmkTAJ4jNQkQtWSWqrXMLK1lLtoV4FmyuQCgsWQQ
dqqFpyT6vLZiEMcVdfMnGlE=
=Zk3y
-----END PGP SIGNATURE-----
--
Rat <ratinox@peorth.gweep.net> \ Happy Fun Ball may stick to certain types
Minion of Nathan - Nathan says Hi! \ of skin.
PGP Key: at a key server near you! \
prev parent reply other threads:[~1999-04-07 21:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-07 16:32 Peter von der Ahé
1999-04-07 17:42 ` Stainless Steel Rat
1999-04-07 19:21 ` Peter von der Ahé
1999-04-07 21:10 ` Stainless Steel Rat [this message]
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=99Apr7.170723edt.13858-3@gateway.intersys.com \
--to=ratinox@peorth.gweep.net \
/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).