[REBOL] Re: Use of 'context
From: brett:codeconscious at: 27-Apr-2001 10:49
In my message I had no desire to have it take anything else. When I said
I was viewing it positively like a database constraint
increases the integrity of a database. Sorry for the ambiguous language.
It was only now that I realised the earlier discussion on this thread had no
highlighting of the new "make object!" behaviour which was introduced in
Core 2.5 - hence my message.
But now that you have asked.
I was musing last night on what the use of N x objects clumped together
would be - even called it a name
n-objects: SITUATION [obj1 obj2 obj3...]
I imagined that if each of these source objects represented an encapsulated
capability than the combined object might in effect be a melding of
capabilities where overlapping fields become the glue of funtionality.
Then I woke up and realised
1) Name clashes between non-glue bits is a pain.
2) N = 2 case is handled by make object object
3) I've just described the global context and modules make come down the
Still it might be nice to have multiple "situations" - but I don't know.
Back to musing. :)