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