[openbeosnetteam] Re: Fwd: NetKit API prototype...

> Well, we won't have one library, we'll have one for C and one for c++
> , so
> having one depend on the other is *BOGUS* and again I will -1 
> attempts to
> drive it down that line.  Again, libnet.so == BSD sockets api, 
> libnetapi.so
> == C++ Be API, they should never meet.

The C++ Be API is just a wrapper for the BSD API, you can still call 
BNetEndpoint::Socket() and use the result with the BSD function set 
without interfering - and we'd have to provide the same functionality.
Of course it's possible to see both, the BSD API and the C++ Be API as 
a wrapper for the net_server functionality, but is it worth the effort 
to develop both of them independently?

> It's *BOGUS* as if I'm writing a c++ app and want to talk to the 
> server
> using C++, why should I have to worry about a C library being loaded 
> with
> all the complications it can cause? No need for it really...

What complications does this cause?

Adios...
   Axel.

Other related posts: