twitter revue moment
M N????.mom => N????.mom +7 -3
@@ 62,7 62,7 @@ .TS ll. Document #: ???? Date: 2021-12-06 Date: 2021-12-07 Project: Programming Language C .PDF_WWW_LINK mailto:nabijaczleweli@nabijaczleweli.xyz PREFIX "Reply-to: наб <" SUFFIX > nabijaczleweli@nabijaczleweli.xyz .TE @@ 71,7 71,7 @@ Project: Programming Language C .HEADING 1 NAMED intro "The issue" .PP The current wording in the current draft C2X standard .PDF_WWW_LINK http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2573.pdf N2573 .PDF_WWW_LINK http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2731.pdf N2731 from 7.27.1.4 is: .in +1cm The range and precision of times representable in \f(CBclock_t\fP and \f(CBtime_t\fP are implementation-defined. @@ 116,7 116,9 @@ struct timespec { }; \*[CONDX] .QUOTE OFF The shortest available \f(CBint64_t\fP is \f(CBlong long\fP \(em a pickle indeed! The shortest available \f(CBint64_t\fP is \f(CBlong long\fP, and the libc \fImust\fP expose a kernel-ABI-compatible \f(CBtimespec\fR \(em a pickle indeed! . .HEADING 1 NAMED wording "Proposed wording" .HEADING 2 NAMED "7.27.1.3" "7.27.1.3" @@ 160,6 162,8 @@ or other processing, and allows user code to actually store it in its original f .HEADING 1 NAMED references "References" The current Linux ABI \f(CBtimespec\fR situation: .PDF_WWW_LINK https://sourceware.org/pipermail/libc-alpha/2021-December/133702.html \(em this is part of a larger thread borne out of an attempt to accurately describe \f(CBtimespec::tv_nsec\fP as part of Linux man-pages' \fBsystem_data_types\fP(7): .PDF_WWW_LINK https://lore.kernel.org/linux-man/ec1dcc655184f6cdaae40ff8b7970b750434e4ef.1638123425.git.nabijaczleweli@nabijaczleweli.xyz/T/ . .PP .br
A README.md => README.md +8 -0
@@ 0,0 1,8 @@ # wg14 [](//builds.sr.ht/~nabijaczleweli/wg14) [](LICENCE) PhD [put me up](//twitter.com/__phantomderp/status/1468040630932750343) to writing WG14 papers :/ ## [PDFs](https://git.sr.ht/~nabijaczleweli/wg14/tree/output/item/README.md) TODO: extract title(s) TODO: add finished ones with numbers