Issue #13095 has been updated by Motohiro KOSAKI.


I disagree.

http://man7.org/linux/man-pages/man2/syscall.2.html clearly explains a caller must care
Architecture-specific requirements. But current this interface have no way Ruby core care
alignment etc.

syscall is misdesigned interface. It assumed old good "integer = pointer = 32bit" world like it born.

----------------------------------------
Feature #13095: [PATCH] io.c (rb_f_syscall): remove deprecation notice
https://bugs.ruby-lang.org/issues/13095#change-62362

* Author: Eric Wong
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
----------------------------------------
io.c (rb_f_syscall): remove deprecation notice

New, perhaps experimental syscalls appear all the time which
may not and never be be supported by the system C library.

Furthermore, on common GNU/Linux platforms, kernel development
and releases happens at a much faster pace than GNU C library
(glibc) development.  In my experience, is more common for users
to run recent, custom-built Linux kernels than a recent,
custom-built glibc.  (This is likely because Linux upstream has
better built-in tooling for distro package management integration
than glibc upstream).

So, ruby should support users who want to deal with the latest
and greatest syscalls in the kernel without having them wait for
C library support.


---Files--------------------------------
0001-io.c-rb_f_syscall-remove-deprecation-notice.patch (1.33 KB)


-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>