Sender: |
|
Date: |
Mon, 2 Jan 2017 10:45:08 +0100 |
MIME-version: |
1.0 (Mac OS X Mail 7.3 \(1878.6\)) |
Reply-To: |
|
Content-type: |
text/plain; charset=windows-1252 |
Subject: |
|
From: |
|
In-Reply-To: |
|
Message-ID: |
|
Content-Transfer-Encoding: |
8bit |
Parts/Attachments: |
|
|
I see no reason why you couldn't have CollectionProperties handle Proxiable. You're right though, it's an obscure case which doesn't make much sense in Java but it might make sense in an external language. Because this is a rare case I need to think about how to implement it, though I don't think it'd be particularly difficult.
Another option would be to do a dynamic proxy (java.util.Propertied). I did that in the Scheme example and it works very nicely.
Sean
On Jan 2, 2017, at 5:20 AM, Abrams, Marshall <[log in to unmask]> wrote:
> I’m wondering whether it would reasonable to add the ability to handle sim.util.Proxiable objects to sim.util.CollectionProperties. Right now, only sim.util.SimpleProperties handles the Proxiable interface. I suspect this change wouldn’t be difficult, but my understanding of the Properties classes is superficial. Maybe it would make sense to move the code that deals with proxy objects into a method in sim.util.Properties. (I’m willing to attempt to make the change if it seems appropriate.)
|
|
|