From: Larry McVoy <lm@mcvoy.com>
To: Jon Steinhart <jon@fourwinds.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Four windowing systems on SunOS
Date: Mon, 31 Oct 2022 12:26:44 -0700 [thread overview]
Message-ID: <20221031192644.GO22806@mcvoy.com> (raw)
In-Reply-To: <202210311917.29VJHxe6110870@darkstar.fourwinds.com>
On Mon, Oct 31, 2022 at 12:17:59PM -0700, Jon Steinhart wrote:
> Larry McVoy writes:
> > Sunview was a toolkit - a really nice one in my opinion, every api had
> > a set of defaults and a key, so you could call sv_whatever(SV_DONE)
> > and did whatever with the default values. But you could override the
> > defaults like so sv_whatever(SV_SOMEKEY, some_value, SV_DONE). It
> > kept the system from being very verbose.
> >
> > People like Sunview's api enough that there was an Xview toolkit which
> > was Sunview ported to X10/X11.
>
> Yeah, but it had its own issues. I did an emergency late night and weekend
> consulting contract with Sun because Xview kept crashing. Turns out that
> the code had some very suspect pointer dereferencing that worked until the
> SPARC processors came along and barfed at unaligned accesses.
Oh yeah, been there, fixed that.
next prev parent reply other threads:[~2022-10-31 19:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 18:21 [TUHS] " Kevin Bowling
2022-10-31 19:14 ` [TUHS] " Larry McVoy
2022-10-31 19:17 ` Jon Steinhart
2022-10-31 19:21 ` Dan Cross
2022-10-31 21:52 ` Grant Taylor via TUHS
2022-11-01 11:02 ` Liam Proven
2022-11-02 8:55 ` Michael Casadevall
2022-11-02 15:34 ` Grant Taylor via TUHS
2022-11-02 15:44 ` Michael Kjörling
2022-11-05 10:38 ` Michael Casadevall
2022-11-05 11:21 ` Liam Proven
2022-10-31 19:26 ` Larry McVoy [this message]
2022-10-31 19:59 ` Ronald Natalie
2022-10-31 19:33 Nelson H. F. Beebe
2022-11-01 3:25 ` Tomasz Rola
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=20221031192644.GO22806@mcvoy.com \
--to=lm@mcvoy.com \
--cc=jon@fourwinds.com \
--cc=tuhs@tuhs.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.
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).