On Wed, Apr 07, 2021 at 09:31:43AM +0200, Morten Brørup wrote: > > I think it's just tradition from Linux/BSD developers not being used to > cross-platform development or having forgotten how to develop software for > deeply embedded systems without a standard O/S below. We use POSIX functions > like sleep() without thinking about it, and simply forget looking for an EAL > variant of the function first. >
it's easy to make this mistake if by including dpdk application headers we indirectly introduce platform specific headers into the applications namespace. if this wasn't happening the application would be forced to confront the issue by directly including unistd.h itself directly making it more obvious that they were writing inherently non-portable code. i think this is being fixed but it is a work in progress but it highlights the reason why there needs to be scrutiny around what goes into the eal and other library headers.
