From: David Hogan <dhog@cs.su.oz.au>
To: sam-fans@hawkwind.utcs.toronto.edu
Date: Mon, 15 Feb 1993 20:11:21 -0500 [thread overview]
Message-ID: <199302161211.25219.out.babun@cs.su.oz.au> (raw)
In-Reply-To: <93Feb15.194907est.2763@hawkwind.utcs.toronto.edu>
> it's probably that the host and terminal exchange a pointer
> in the protocol and it's known to fit in 4 bytes.
> you'll need to fuss with the protocol, making it
> incompatible with other architectures. sigh.
> -rob
One way of doing this would be to replace the pointers in the
protocol with 32 bit offsets from the start of the arena. That
way, unless the arena grows to be greater than 4 gigabytes (!) 4
bytes will still be adequate, and the modified samterm should still
interoperate with sams on other architectures.
prev parent reply other threads:[~1993-02-16 1:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-02-16 0:47 rob
1993-02-16 1:11 ` David Hogan [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=199302161211.25219.out.babun@cs.su.oz.au \
--to=dhog@cs.su.oz.au \
--cc=sam-fans@hawkwind.utcs.toronto.edu \
/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).