From: Andy Wingo <wingo@pobox.com>
To: NalaGinrut@gmail.com
Cc: Guile <guile-user@gnu.org>, Neil Jerram <neil@ossau.uklinux.net>
Subject: Re: Is there any approach to define "private" vars in GOOPS?
Date: Wed, 09 Mar 2011 23:19:54 +0100 [thread overview]
Message-ID: <m37hc86inp.fsf@unquote.localdomain> (raw)
In-Reply-To: <1299663423.2577.86.camel@Renee-desktop> (nalaginrut@gmail.com's message of "Wed, 09 Mar 2011 17:37:03 +0800")
On Wed 09 Mar 2011 10:37, nalaginrut <nalaginrut@gmail.com> writes:
> But I still want to talk this topic: "How to hide the critical
> property?"
I don't know what the GOOPS / CLOS answer is to this, but more
generally, you might enjoy the following paper:
http://mumble.net/~jar/pubs/secureos/
Regards,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-03-09 22:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 2:37 Is there any approach to define "private" vars in GOOPS? nalaginrut
2011-03-09 8:46 ` Neil Jerram
2011-03-09 9:27 ` nalaginrut
2011-03-09 9:37 ` nalaginrut
2011-03-09 22:19 ` Andy Wingo [this message]
2011-04-01 22:55 ` Neil Jerram
2011-03-09 9:46 ` Mark H Weaver
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=m37hc86inp.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=NalaGinrut@gmail.com \
--cc=guile-user@gnu.org \
--cc=neil@ossau.uklinux.net \
/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).