Bertrand Coconnier

@mike402 Thanks for this proposal but instead of implementing these functions in C++, I'd rather extend the concept of "template" functions that have been designed for unit conversion (see [scripts/unitconversions.xml](https://github.com/JSBSim-Team/jsbsim/blob/master/scripts/unitconversions.xml))....

> does it depend on C++ in other way than loading an extra xml that would be the new "library"? Yes, it needs additional C++ code. At the moment, if...

From @mike402 suggested in issue #124 that has been marked as a duplicate of the current issue: > ``, `` and `` would have been very convenient, because their equivalents...

@mike402 > ``, `` and `` would have been very convenient, because their equivalents are very bulky and typo-prone. These 3 functions have just been added to `` via the...

> These 3 functions have just been added to `` via the commit f0d67c8. And they are now pushed to FlightGear as well.

Indeed these warnings are not linked to FlightGear. But this might need some work to make this warning messages context sensitive.

@mike402 The last commit to FlightGear might alos possibly reduce the number of spurious warnings. JSBSim now makes an extended use of its class `FGPropertyValue` for sensors which allows late...

@NikolaiVChr The purpose is not to suppress these warnings messages altogether but rather to make sure that they are issued only when relevant.

> What about the remaining warning in `FGPropertyReader.cpp` around line `Property ... is already defined`? > > There is really no way to go without `` declarations in the system...

> By the way, it might be a separate issue but `` of `` `` requires its inputs to be declared as ``, even if such filter exists and even...