Hi there, Graham Barr dixit:
> > @ISA = qw(Exporter); > > > > @EXPORT_OK = qw( &host_ip ); > > Change that to @EXPORT instead of @EXPORT_OK > > Graham. Done and it's working... I thought I had tried that one, though... Thanks! It will go to Net::LDAP::Extra::introspection where I'll have some functions to inspect the objects at runtime... My only concern is that I make heavy use of LDAP objects in my application, will this incur into a big penalization in terms of runtime? I can, of course, modify my own classes to handle such data, but this is actually what I'd like, and it's transparent to the rest of my code, therefore the 'perfect' solution. Maybe an introspection API could be introduced at a later version of perl-ldap? While most of the time we know the data we want to use to connect/search/etc introspection functions can be useful where objects are passed between functions and connections are performed automagically (as it's my case). Lastly, is there any examples of using callbacks to handle, say, referals? >From my doc reading, they can be handled when doing searches, but my main problems come from read-only LDAPs when updating data... thanks for all and keep up the great work! david
