The other style:

hb_socket_accept()
hb_socket_bind()
hb_socket_close()
hb_socket_connect()
hb_socket_create()
hb_socket_error()
hb_socket_exit()
hb_socket_getpeername()
hb_socket_getsockname()
hb_socket_init()
hb_socket_listen()
hb_socket_recv()
hb_socket_select()
hb_socket_send()
hb_socket_shutdown()


On Thu, Jun 18, 2009 at 8:59 AM, Viktor Szakáts <[email protected]>wrote:

> These are the calls of Mindaugas's socket API:
> hb_socketAccept()
> hb_socketBind()
> hb_socketClose()
> hb_socketConnect()
> hb_socketCreate()
> hb_socketError()
> hb_socketExit()
> hb_socketGetPeerName()
> hb_socketGetSockName()
> hb_socketInit()
> hb_socketListen()
> hb_socketRecv()
> hb_socketSelect()
> hb_socketSend()
> hb_socketShutdown()
>
> Brgds,
> Viktor
>
>
> On Thu, Jun 18, 2009 at 12:08 AM, Viktor Szakáts <[email protected]>wrote:
>
>> Hi All,
>>
>> Is there any objections in adding new socket API
>> developed by Mindaugas to core RTL lib?
>>
>> To me it seems a better / cleaner implementation,
>> with a more natural Harbour level API. It's also
>> friendlier with MT.
>>
>> Current hb_inet*() API has some other problems,
>> and it was planned to be replaced.
>>
>> So, the idea here is that I add now socket.c to
>> core, we will fill the missing gaps, at the same
>> time users can start to get familiar with it and
>> if everything is okay with it, we promote it as
>> the primary "inet" API of Harbour. In the future
>> or at the same time we retire the old API with a
>> future HB_LEGACY_LEVEL (and/or move it to a separate
>> contrib, or xhb lib or an example lib).
>>
>> To match Harbour core naming scheme, I'd like to
>> rename all functions from SOCKET_*() to HB_SOCKET*().
>>
>> (if group thinks we may retain the second
>> underscore - HB_SOCKET_*() to resemble to low level
>> socket functions, although this kind of naming style
>> is unusual in our core)
>>
>> Opinions?
>>
>> Brgds,
>> Viktor
>>
>>
>
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to