Bugzilla – Bug 2163
introspection not finding mesh config paths
Last modified: 2019-11-05 18:55:01 UTC
Mesh-related objects are aggregated to MeshPointDevice, and are accessible via config paths such as: /$ns3::NodeListPriv/NodeList/*/$ns3::Node/DeviceList/*/$ns3::MeshPointDevice/$ns3::dot11s::PeerManagementProtocol/LinkOpen However, the introspection program is not picking up these possible config paths: https://www.nsnam.org/docs/release/3.23/doxygen/classns3_1_1dot11s_1_1_peer_management_protocol.html#details I don't know whether this is limited to 'mesh' module (e.g. 'aodv' is also in a separate namespace) and I suspect that the placement of these objects in namespace dot11s is the reason the introspection program is not finding them.
I think GetTypicalAggregations() of print-introspected-doxygen.cc is the right place to record these other aggregations. https://www.nsnam.org/docs/doxygen/print-introspected-doxygen_8cc_source.html#l01276 For example, these inner namespace items are recorded: ns3::aodv::RoutingProtocol ns3::dsdv::RoutingProtocol ns3::dsr::DsrRouting ns3::olsr::RoutingProtocol What mesh-related objects are not being picked up?