Re: RTT-Introspection and how to do it ?

Am 30.03.2015 um 14:56 schrieb Sylvain Joyeux:
> ... coming back to my previous point:
>   - the connection manager and channels APIs are private and should not
> directly be accessed for this purpose
Hu ? The conn manager is public in PortInterface, and the documentation
says it may be used for exactly this purpose :

         /**
          * Returns the connection manager of this port (if any).
          * This method provides access to the internals of this port
          * in order to allow connection introspection.
          * @return null if no such manager is available, or the manager
          * otherwise.
          * @see ConnectionManager::getChannels() for a list of all
          * connections of this port.
          */
         virtual const internal::ConnectionManager* getManager() const = 0;

>
> Moreover, if you aim is to make the connection info feature available
> to everyone, then adding it to the public API would make sense.
It is public in the sense, that you can use it if you compile and
install the query library and it's service. I don't see a point of
adding it into the RTT core thou.
Greetings
     Janosch


-- 
  Dipl. Inf. Janosch Machowinski
  SAR- & Sicherheitsrobotik

  Universität Bremen
  FB 3 - Mathematik und Informatik
  AG Robotik
  Robert-Hooke-Straße 1
  28359 Bremen, Germany
  
  Zentrale: +49 421 178 45-6611
  
  Besuchsadresse der Nebengeschäftstelle:
  Robert-Hooke-Straße 5
  28359 Bremen, Germany
  
  Tel.:    +49 421 178 45-6614
  Empfang: +49 421 178 45-6600
  Fax:     +49 421 178 45-4150
  E-Mail:  [email protected]

  Weitere Informationen: http://www.informatik.uni-bremen.de/robotik

-- 
Orocos-Dev mailing list
[email protected]
http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev