From: Clinton Ebadi <clinton@unknownlamer.org>
To: guile-user@gnu.org
Subject: Re: [patch] subordinate SMOBs with GOOPS superclasses
Date: Thu, 13 Dec 2007 08:23:57 -0500 [thread overview]
Message-ID: <87hcimafte.fsf@unknownlamer.org> (raw)
In-Reply-To: <20071212.224151.74751067.schilling.klaus@web.de> (Klaus Schilling's message of "Wed\, 12 Dec 2007 22\:41\:51 +0100 \(CET\)")
Klaus Schilling <schilling.klaus@web.de> writes:
> From: Clinton Ebadi <clinton@unknownlamer.org>
> Subject: Re: [patch] subordinate SMOBs with GOOPS superclasses
> Date: Wed, 12 Dec 2007 15:38:03 -0500
>> and not abort the entire system. At least in SBCL it takes a lot of
>> abuse before a C library can crash anything.
>
> That's completely illicit, as SBCL
> is of no use whatsoever as an embeddable extension library.
I fail to see how SBCL not being embeddeable annuls my
argument. S/SBCL/Clisp/ and the same argument applies; illegal
instructions or segmentation violations that don't smash the stack or
corrupt the heap is recoverable.
--
emacsen: "Like... windows are portals man...
emacsen: Dude... let's yank this shit out of the kill ring"
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
parent reply other threads:[~2007-12-13 13:23 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20071212.224151.74751067.schilling.klaus@web.de>]
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87hcimafte.fsf@unknownlamer.org \
--to=clinton@unknownlamer.org \
--cc=guile-user@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).