[olsr-dev] some Qs about exending the dyn_gw plugin

Jens Nachtigall (spam-protected)
Sat Nov 6 01:35:19 CET 2004

> There is a new interface for this in current CVS. The plugin loader
> will try to fetch a function called register_olsr_param typed to: int
> (*register_param)(char *, char *);

You mean, 
int register_olsr_param(char *one,char *two)
don't you?

Afaics olsrd does not catch the return value from register_olsr_param:
   printf("\tKey:\"%s\" value:\"%s\"\n", params->key, params->value);
   entry->register_param(params->key, params->value);
   params = params->next;

I think, this would be a good idea, in case the users enters an option, 
which is not available/allowed. I could, of course also call exit(), or 
whatever myself. But giving back a return value from 
register_olsr_param meaning "configuration error" (e.g. 0) , and having 
then olsrd react according to its general policy is better imho.

Please bare with me, if I ask/say something stupid. I'm not a very 
experienced programmer.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20041106/8886696b/attachment.sig>

More information about the Olsr-dev mailing list