From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <2a79a565395945cd1a40d7c74d6a53b9@quanstro.net>
From: erik quanstrom <quanstro@quanstro.net>
Date: Fri, 28 Apr 2006 08:30:11 -0500
To: 9fans@cse.psu.edu
Subject: Re: [9fans] too good to pass up (SRB Comments)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 49f99f7a-ead1-11e9-9d60-3106f5b1d025

it was not cleaned up in the xinu bsd source.  iirc, on a vax,
it would coredump fairly reliably.  i spent some time trying
to figure out what the malfunction was, but never could.

i blamed nfs, since it was the convient thing to do, and
started using byron's rc.

the coding style was never a significant problem.  if it were,
i could have easily written a script to replace the odd #defines.

- erik

On Fri Apr 28 08:12:19 CDT 2006, brantley@coraid.com wrote:
> That was really John Mashy's fault, as I understand it.  He suggested
> it to SRB.  I had to deal with it when I ported V7 to the 68K.  Too
> bad every processor wasn't as clean in this reguard as the PDP-11.
>
> For those who might not have heard of this, SRB caught segfault
> signals, allocated more memory and just returned.  The instruction
> that caused the segfault would restart.  It was an automatic memory
> allocator.  Problem was that not all processors could pull off this
> sort of stunt.
>
> Geoff cleaned this up years ago.
>
> > not even his allocator?
> >
> > - erik
> >
> > On Fri Apr 28 08:02:29 CDT 2006, brantley@coraid.com wrote:
> >> > Not that I'm defending writing C as
> >> > though it were Algol 68...
> >>
> >> I kind of liked it after the initial shock.
> >> Even inspired the Obfuscated C Contest.
> >> I don't think SRB's code was obfuscated, though.
> >>
> >>
>
>