[Meta,OT] OOP and Forks
[Meta,OT] OOP and Forks
- Subject: [Meta,OT] OOP and Forks
- From: email@hidden
- Date: Fri, 1 Feb 2002 01:57:59 EST
I'm a bit puzzled philosophically. Maybe someone can shed some light.
When the Mac was created, Apple decided that files of all types should have
resource forks and data (including programming code) forks. This basically
kept the nouns and verbs separated, and allowed fascinating things like
ResEdit to exist. IMHO, it was brilliant.
OOP, as I grok it, involves "objects" which internally contain their own
nouns and verbs and you don't need to know anything about them, just enter
thru the front door and pay your money please.
These seem like two very different ways to structure things.
For me, I very much like the idea that nouns and verbs (data and code) are
separate. The only nouns I let my objects have are throw-away temp variables
and data structures built dynamically from a common source. That way,
multiple different handlers can each work with the same data.
Am I missing something? Is this a meaningful paradox/dichotomy that I am
seeing? Can both philosophies coexist in a Mac/Unix world?
Jeff Baumann
email@hidden
www.linkedresources.com