From: "matt" <matt@proweb.co.uk>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] OO plan 9
Date: Mon, 2 Sep 2002 16:04:03 +0100 [thread overview]
Message-ID: <00be01c25291$fabe0d50$6501a8c0@KIKE> (raw)
In-Reply-To: <e40f86f6acaae338e8f5308585f3021d@plan9.bell-labs.com>
I would contend that the OO concepts of polymorphism, inheritance can be
expressed through mount and bind.
It would be farily trivial to write class factories with rc.
It just so happens that most of the supplied 'objects' are application
sized.
Besides OO is just a struct with a pointer to itself and all of it's
functions, the rest is just syntax and macros ;)
m
---
Outgoing mail is certified as a Virus.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.384 / Virus Database: 216 - Release Date: 21/08/2002
next prev parent reply other threads:[~2002-09-02 15:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-02 14:44 [9fans] " Russ Cox
2002-09-02 15:04 ` matt [this message]
2002-09-04 2:37 ` Eric Dorman
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='00be01c25291$fabe0d50$6501a8c0@KIKE' \
--to=matt@proweb.co.uk \
--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).