zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
To: zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: endianness of wordcode
Date: Thu, 23 Mar 2000 21:04:32 +0000	[thread overview]
Message-ID: <E12YbFr-0003N4-00.2000-03-24-21-04-27@mail12.svr.pol.co.uk> (raw)

I'm a little doubtful about the necessity of having doubled wordcode files
for different endianness.  It's only useful when sharing files across
heterogeneous networks --- you wouldn't distribute wordcode files, you'd
compile them in situ (or at least I would).  I wonder whether it would be
better always to dump in the native format, check if the order is swapped
when reading, and if so swap it back on the fly.  That's a fairly trivial
operation compared with all the rest of the stuff zsh is going to be doing
with the extracted code.

In fact, the code I stole as the basis for the pattern-matching equivalent
of wordcode explicitly reconstructs integers by shifting and or'ing,
probably without even the intention of making it machine-independent since
the compiled patterns were for internal use.

I think the zcompile documentation, and maybe other places where wordcode
is mentioned, could be friendlier: it introduces the (non-existent?) word
`wordcode' with no explanation, and you really don't even need to know that
it exists, only that there is a black box which produces versions of
functions that load faster and maybe save memory.

-- 
Peter Stephenson <pws@pwstephenson.fsnet.co.uk>


             reply	other threads:[~2000-03-24 21:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-23 21:04 Peter Stephenson [this message]
2000-03-25 20:39 ` Bart Schaefer
2000-03-27  8:32 Sven Wischnowsky
2000-03-27 11:43 Sven Wischnowsky
2000-03-27 16:28 ` Bart Schaefer

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=E12YbFr-0003N4-00.2000-03-24-21-04-27@mail12.svr.pol.co.uk \
    --to=pws@pwstephenson.fsnet.co.uk \
    --cc=zsh-workers@sunsite.auc.dk \
    /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.vuxu.org/mirror/zsh/

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).