Daniel Stenberg wrote:
> > Are there both non-_ex and _ex versions of those functions?
> > Otherwise might as well clean up the names before 1.0.
>
> I believe it is always the case of the _ex being the actual
> function and the non-_ex being a macro that uses the _ex function.
What macros?
$ grep -r libssh2_sftp_open .
./libssh2_priv.h: /* State variables used in libssh2_sftp_open_ex() */
./sftp.c:/* {{{ libssh2_sftp_open_ex
./sftp.c:libssh2_sftp_open_ex(LIBSSH2_SFTP * sftp, const char *filename,
$ grep -r libssh2_channel_read .
./channel.c: * {{{ libssh2_channel_read_ex
./channel.c:libssh2_channel_read_ex(LIBSSH2_CHANNEL * channel, int stream_id,
char *buf,
./libssh2_priv.h: /* State variables used in libssh2_channel_read_ex() */
./publickey.c: rc = libssh2_channel_read_ex(channel, 0, (char *) buffer,
4);
./publickey.c: rc = libssh2_channel_read_ex(channel, 0, (char *)
pkey->receive_packet,
./scp.c: rc = libssh2_channel_read_ex(session->scpRecv_channel,
0,
..more hits..
> Of course, both the macro and the actual function are part of the
> API while the function only is the ABI. So I'm not sure what the
> most sensible way is to name the files...
I say yank out _ex from all functions.
//Peter
------------------------------------------------------------------------------
_______________________________________________
libssh2-devel mailing list
libssh2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libssh2-devel
