aboutsummaryrefslogtreecommitdiff
path: root/usr.bin/posixmqcontrol/(public-mirror)
diff options
context:
space:
mode:
authorMark Johnston <markj@FreeBSD.org>2025-07-07 15:43:27 +0000
committerMark Johnston <markj@FreeBSD.org>2025-07-07 15:43:27 +0000
commiteda96744b434325c475dce449744f2268f1033e8 (patch)
treea11f5f08db8f900f783fa5c6a74c039702650da7 /usr.bin/posixmqcontrol/(public-mirror)
parent9940c974029ba53fc00696b3fa1784725c48a9e9 (diff)
lposix: Clean up the posix namespace definitionsHEADmain
The posix module is subdivided according to C headers; for instance, posix.unistd contains routines available from unistd.h, such as chown(2). A quirk of our implementation is that each of the modules is a direct entry in the global table. That is, there is no "posix" table. Instead, "posix.foo" and "posix.bar.baz" are both top-level tables. This is surprising and goes against Lua's shorthand of using "." to access keys in a table. lua-posix also doesn't work this way. Rework things so that "posix" and "posix.sys" are proper tables. Existing flua code which uses require() to bind posix submodules to a name will be unaffected. Code which accesses them directly using something like _G["posix.sys.utsname"].uname() will be broken, but I don't think anything like that exists. In particular, it is now possible to call posix.sys.utsname.uname() without any require statements. Reviewed by: imp, bapt MFC after: 2 weeks Differential Revision: https://reviews.freebsd.org/D51158
Diffstat (limited to 'usr.bin/posixmqcontrol/(public-mirror)')
0 files changed, 0 insertions, 0 deletions