Re: Re: Proposal: System Object Tree

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 17 September 2003 02:13 am, H. Peter Anvin wrote:
> I would rather suggest doing:
>
> $core.foo and $core:bar()... i.e. instead of having the system object be
> the source of these, simply mark which core you want to talk to, and let
> #0 be the source of pointers to those system objects.
Except what I need is completely independant cores within the same MOO. For=
=20
example, a LambdaCore, a JHCore, and some other obscure core. Each of these=
=20
would have to work with their own bf_* and generics. And then afterward the=
y=20
need to be seperated again and still work properly.
The idea behind the System Object Tree allows me to make a 'system' propert=
y=20
on that core's Root Object (or equivalent) pointing to that core's System=20
Object.
>
> Otherwise you're going to have conflicts no matter what you do.
What conflicts are you referring to? There are no conflicts that I can see =
in=20
my original idea...
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/jYbLZl/BHdU+lYMRApgDAJ9MqWspZdtyPO2ur338QpomdLkp/ACfXzyA
oyA8oC5yHCxyRWomexX+BrU=3D
=3DF1CY
=2D----END PGP SIGNATURE-----



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php