Re:C library system-call wrappers, or the lack thereof
by bogomipz on Wednesday November 14, 2018 @10:37AM
(#18450621)
The post states:
>"In such cases, user-space developers must fall back on syscall() to access that functionality, an approach that is both non-portable and error-prone."
I understand about portability but can someone elaborate on why using syscall() is inherently error-prone?
>"In such cases, user-space developers must fall back on syscall() to access that functionality, an approach that is both non-portable and error-prone."
I understand about portability but can someone elaborate on why using syscall() is inherently error-prone?