From: "Eric M. Ludlam" <eric@siege-engine.com>
Cc: emacs-devel@gnu.org
Subject: Re[3]: struct.el -- a package to encode/decode binary data
Date: Tue, 19 Mar 2002 08:26:57 -0500 [thread overview]
Message-ID: <200203191326.g2JDQvO20890@beta.siege-engine.com> (raw)
In-Reply-To: <5xlmcod8cg.fsf@kfs2.cua.dk> (storm@cua.dk)
>>> storm@cua.dk (Kim F. Storm) seems to think that:
>"Eric M. Ludlam" <eric@siege-engine.com> writes:
>
>> I wrote something for packing X messages via a TCP socket. You could
>> define the message in a vector and it would pack and unpack the item.
>> It was X centric, and you could encode sizes for X's dynamic length
>> fields.
>
>I looked at your code, and I can see we are touching on similar
>grounds here, but there are quite fundamental differences in each
>approach, so I guess both packages will have their uses (and users).
>
>Notably, my package separates format and data in a pretty generic way,
>while your package tends to mix data and format which is less generic,
>but probably somewhat easier to use for some purposes.
>
>Also, your package has much more versatile ways of recognizing /
>guessing the actual format of some data -- but I think that part is
>pretty X-centric in its current form.
>
>I'll probably have to look into this aspect for my package to be
>more complete (I have some ideas about how to add `union' support).
It has been quite some time since I wrote or even looked in that
package. I wanted to draw nifty pictures from Emacs Lisp but it was
way more work just getting the graphics up, never mind writing an
app. ;)
My other Emacs/TCP/UDP app is gtalk (gnutalk.sourceforge.net) but that
used an external C package. No one seems to use that protocol these
days though. :(
Have fun
Eric
--
Eric Ludlam: zappo@gnu.org, eric@siege-engine.com
Home: www.ultranet.com/~zappo Siege: www.siege-engine.com
Emacs: http://cedet.sourceforge.net GNU: www.gnu.org
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-03-19 13:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-18 23:12 struct.el -- a package to encode/decode binary data Kim F. Storm
2002-03-19 0:25 ` Miles Bader
2002-03-19 1:38 ` Re[1]: " Eric M. Ludlam
2002-03-19 12:56 ` Kim F. Storm
2002-03-19 13:26 ` Eric M. Ludlam [this message]
2002-03-19 7:02 ` Eli Zaretskii
2002-03-19 12:34 ` Stefan Monnier
2002-03-19 14:38 ` Eli Zaretskii
2002-03-19 14:33 ` Luke Gorrie
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=200203191326.g2JDQvO20890@beta.siege-engine.com \
--to=eric@siege-engine.com \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).