> It has another interesting feature, suggested by ThorstenB - if you try > to read an invalid path, it doesn't silently succeed - it throws an > exception! This is to avoid lurking typos in property paths, which has > been an issue. (I will be adding a 'weak' variant, that takes a default > value, for the cases where people want to read a property that might > not exist) > > ... > > I'm not going to start converting tied properties to use > propertyObjects next week, or next month, but certainly next year. The > hope is that by that time, this code is mature, efficient and so on - > so please try it, use it and fix it! > > Regards, > James
This concerns me a bit. JSBSim grabs a copy of the relevant simgear code to support properties once every couple of years. When JSBSim is built within FlightGear, we of course just use what's there in the FlightGear tree. But, when JSBSim is incorporated into other products, they use what we have in our codebase. I'm concerned that at some point the property system will evolve to the point where serious conflicts arise, and backwards compatibility is broken. We (JSBSim) depend on the property system. I'm wondering if the property code should just be left well enough alone... Jon ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
