Hi Steven, I did a quick research of these functions. Some of them should be library APIs and some should be internal only That is what I found: These are used only in the library, going to hide them: tep_peek_char tep_buffer_init tep_get_input_buf_ptr tep_get_input_buf tep_read_token tep_free_token These are used by perf and trace-cmd, going to add a man page for them: tep_print_printk tep_add_plugin_path tep_print_funcs These are not used anywhere yet, but look like APIs, going to add a man page for them: tep_set_test_filters tep_plugin_print_options This one is already an API with man page, it is in the list by mistake tep_load_plugins_hook On Mon, Sep 21, 2020 at 7:22 AM Tzvetomir Stoyanov <tz.stoyanov@xxxxxxxxx> wrote: > > Hi Steven, > While I was working to hide non API libtraceevent functions from the > users, as Ben Hutchings suggested, I found these - they are declared > as official APIs in event-parse.h, but are not described in the man > pages. We should decide - are they APIs, so we should add them into > the man pages, or are internal functions and we should hide them. > tep_peek_char > tep_load_plugins_hook > tep_print_printk > tep_buffer_init > tep_get_input_buf_ptr > tep_get_input_buf > tep_read_token > tep_set_test_filters > tep_add_plugin_path > tep_plugin_print_options > tep_free_token > tep_print_funcs > > -- > Tzvetomir (Ceco) Stoyanov > VMware Open Source Technology Center -- Tzvetomir (Ceco) Stoyanov VMware Open Source Technology Center
|