FreeLists / openbeosnetteam / [openbeosnetteam] Re: Networking and the new Build System

[Philippe Houdoin <philippe.houdoin@xxxxxxx>]

> As you should best know, we are not 100% source compatible -- the networking
> stuff is an excellent example.

The worst, too. :-\

> > I really dunno how we could fix it so it works fine for all three source
> > uncompatible network environment. Well, two, as our public headers should
> be
> > source compatible with BONE/Dano/Zeta ones, just located under POSIX
> > instead of
> > headers/be/bone/*
>
> Maybe putting them into a separate header tree isn't that bad an idea. At
> least it would solve the problem, that you can't use the networking headers
> without also getting all the other POSIX headers.

Yes, maybe it's the way to go. Maybe I should move our networking POSIX headers
out of POSIX and back to our headers/os/net and just turn our
headers/posix/[i]net headers into wrappers.

> OK, then I'll see, how far I get first. I would be delighted to hear, what to
> do about the usage of the atomic_add64() function, that doesn't exists under
> BeOS R5 (unless I'm not mistaken).

I think it's a haiku exclusivity too.

Waldemar, why 64bits here? Mandatory? Can't we use uint32 and atomic_add()
instead?

- Philippe

PS: I'm off for 5 days vacations.
--