Re: [boost] interest in properties library

Hello, Daniel.
Saturday, December 20, 2008 at 4:29:53 PM you wrote:
DO> What I still want to do is enable simpler syntax and maybe signals DO> triggered by property and other goodies, but that is actually rather DO> simple to do, using bind and/or lambda.
Some time ago I showed another way to define properties for the class. I think what this way quite simpler. Take a look:
Hi. I saw this in the list. I like the notational simplicity, but it does it allow run-time addressing of properties (i.e. scripting, setting properties from config files) and accessing properties without knowing the full type? The latter becomes important when you don't want to include headers for everything or load additional classes through plugins. I have also found some properties stuff in the sandbox, especially one that nice handles property graphs, but none fulfilled the above requirements. So maybe this is too specialized? I thought it would be a great way to allow scriptable access to properties of classes that are not known at compile time, and thereby allow easy runtime setup of a modular system. Thanks for the replies though, some interesting thoughts. Daniel

Hello, Daniel. Monday, December 22, 2008 at 1:39:19 AM you wrote: DO> Hi. DO> I saw this in the list. I like the notational simplicity, but it does DO> it allow run-time addressing of properties (i.e. scripting, setting DO> properties from config files) and accessing properties without knowing DO> the full type? I'm planning to implement such functionality for the same reasons. In theory it is possible at least with help of 'variant' types. Also I think it is possibly to combine compiletime-defined and runtime-defined properties. -- Best Regards, Sergey mailto:flex_ferrum@artberg.ru
participants (2)
-
Daniel Oberhoff
-
Sergey Sadovnikov