Hi, I found that if a pair of functions available, e.g. gda_connection_get_meta_store_data_v and gda_connection_get_meta_store_data
the one with suffix _v only accept GList* type, while the "normal" function accepts undefined number of parameters (...) As results, it is convenient to wrap (e.g. bind to C++) "normal" function using _v function. However, I found that this rule was broken in master branch at least for one object. gda_server_operation_prepare_create_table accepts GList* parameter, while corresponding _v function accepts undefined number of parameters. In this case wrapping is much easier, because _v function may be just ignored. Could you please add some comments here or explain internal policy of naming functions for _v cases? Thanks. -- - Pavlo Solntsev --------------------------------------------- Sent from Evolution on GNU/Debian <www.debian.org> id="-x-evo- selection-start-marker"> _______________________________________________ gnome-db-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/gnome-db-list
