unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@is.elta.co.il>
Cc: emacs-devel@gnu.org, Kenichi Handa <handa@etl.go.jp>
Subject: Re: struct.el -- a package to encode/decode binary data
Date: Tue, 19 Mar 2002 09:02:19 +0200 (IST)	[thread overview]
Message-ID: <Pine.SUN.3.91.1020319085342.15195H-100000@is> (raw)
In-Reply-To: <5x1yehpj1w.fsf@kfs2.cua.dk>


On 19 Mar 2002, Kim F. Storm wrote:

> While writing a package that sends and receives datagrams using the
> new make-network-process functionality, I quickly found that I needed
> to be able to encode and decode binary data structures, so I came up
> with the following package (struct.el).
> 
> I'd like to hear if something like this already exists, or if others
> find it should be added to emacs (with more complete documentation of
> course).  [Also, the struct-pack function doesn't work with nested
> data, but I'll fix that if there is an interest in this package].

I think it would be a very useful addition to Emacs, but I have one
comment about the implementation: I don't like (and that's an
understatement!) the idea of using unibyte strings.  I especially get 
shivers when I see string-make-unibyte and its ilk.

Unibyte strings and buffers are The Mother Of All Evil in Emacs--they are
the primary reason for those pesky \201 characters popping up in user
buffers.  Thanks to titanic effort of Handa-san and others, Emacs mostly
does TRT with unibyte text, but I think we shouldn't test that too much
for our own good, especially in a package bundled with Emacs. 

If I understand correctly what you want to do, there should be no reason 
for unibyte text in your implementation.  Emacs should be able to deal 
with binary data as multibyte, just be sure to decode it as raw-text-unix.

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel


  parent reply	other threads:[~2002-03-19  7:02 UTC|newest]

Thread overview: 27+ 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     ` Re[3]: " Eric M. Ludlam
2002-03-19  7:02 ` Eli Zaretskii [this message]
2002-03-19 12:34   ` Stefan Monnier
2002-03-19 14:38     ` Eli Zaretskii
2002-03-19 14:33 ` Luke Gorrie
     [not found] <Pine.SUN.3.91.1020319133840.17982G-100000@is>
2002-03-19 14:34 ` Kim F. Storm
2002-03-19 21:27   ` Thien-Thi Nguyen
2002-03-21  9:04   ` Richard Stallman
2002-03-21 11:15     ` Eli Zaretskii
2002-03-21 13:31       ` Kim F. Storm
2002-03-21 14:56         ` Eli Zaretskii
2002-03-21 15:36           ` Kim F. Storm
2002-03-21 16:58             ` Stefan Monnier
2002-03-21 19:45               ` Eli Zaretskii
2002-03-22  1:05                 ` Stefan Monnier
2002-03-22 11:04                   ` Eli Zaretskii
2002-03-22  0:37           ` Miles Bader
2002-03-23  2:35           ` Richard Stallman
2002-03-21 16:53         ` Stefan Monnier
2002-03-23  2:36       ` Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2002-03-22  1:25 Kenichi Handa
2002-03-22  1:27 ` Stefan Monnier
2002-03-22  1:30 Kenichi Handa

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=Pine.SUN.3.91.1020319085342.15195H-100000@is \
    --to=eliz@is.elta.co.il \
    --cc=emacs-devel@gnu.org \
    --cc=handa@etl.go.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.
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).