From: Brantley Coile <brantley@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] too good to pass up (SRB Comments)
Date: Fri, 28 Apr 2006 09:10:26 -0400 [thread overview]
Message-ID: <790d46fb49d0b5be9d9300797ec1e698@coraid.com> (raw)
In-Reply-To: <d95f31573a6820f5d27d18130cc49c2e@quanstro.net>
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.
>>
>>
next prev parent reply other threads:[~2006-04-28 13:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-28 13:01 [9fans] too good to pass up erik quanstrom
2006-04-28 13:10 ` Brantley Coile [this message]
2006-04-28 14:16 ` OT: Re: [9fans] too good to pass up (SRB Comments) Dave Lukes
2006-04-28 14:18 ` Brantley Coile
2006-05-02 6:32 ` Roman Shaposhnik
2006-05-01 21:22 ` Taj Khattra
2006-04-28 21:57 ` [9fans] too good to pass up Charles Forsyth
2006-04-28 13:30 [9fans] too good to pass up (SRB Comments) erik quanstrom
2006-04-28 21:13 ` geoff
2006-04-28 21:06 ` quanstro
2006-04-30 10:35 ` Richard Miller
2006-05-01 1:01 ` geoff
2006-05-01 9:21 ` Richard Miller
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=790d46fb49d0b5be9d9300797ec1e698@coraid.com \
--to=brantley@coraid.com \
--cc=9fans@cse.psu.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).