Repository navigation
0.16.0 --- a least stack size, whether input is altered, and what closing a directory ends - #50
Merged
Merged
Conversation
…what closing a directory ends kal_task_start_sized starts a context whose stack is at least the size asked for; a request beyond what the environment can give is kal_err_no_memory, the outcome kal_alloc reports when it is exhausted (clause 3.1). KAL_TERM_PASS_INPUT states that what is typed reaches the program as the keystrokes produced it. KAL_TERM_PASS_CONTROL keeps its meaning, and its paragraph no longer claims the bytes arrive unaltered. fs.h states what closing a directory does to its enumerations, and that kal_fs_list_next refuses a closed directory. Clause 11 entries 22 to 24, and a conformance observation of the least size.
Its console consumes Ctrl+J in raw mode unless its own switch for delivering what a key produces is on, and its line assembly alters input whatever it is asked; with the position set, all three deliver 0x0d and 0x0a.
…L's paragraph reads in its original order
…tion: not an error, distinguished or zero, and put back
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #48.
Three changes, each an addition under clause 8; no existing declaration changes.
kal_task_start_sizedstarts a context whose stack is at least the size asked for, as the context is told bykal_task_stack. A request the environment cannot meet iskal_err_no_memory, the outcomekal_allocreports when exhausted (clause 3.1); it is not a refusal (clause 6.1), and no capability position is needed. Version 0.15 called the size "a property rather than a parameter" and offered no enquiry that reported it (mcpplibs/openkal-musl#48).KAL_TERM_PASS_INPUT(bit 3) states that what is typed arrives as the keystrokes produced it. It is independent ofKAL_TERM_PASS_CONTROL, whose paragraph no longer claims the bytes arrive unaltered, and covers every mechanism by which an environment alters input. With it set, the return key is 0x0d and Ctrl+J is 0x0a on all three environments, measured: two of them rewrite the return key into a line feed when it is clear, and the third consumes Ctrl+J.fs.hstates what closing a directory does to its enumerations: the directory is a released handle, andkal_fs_list_nextgiven it refuses (mcpplibs/openkal-linux#34).Clause 11 entries 22 to 24 record each. The suite observes a least stack size as room (a recursion of three quarters of a 4 MiB request completes) and the input position as it observes the control position. The design and its review are
.agents/docs/2026-10-25-three-reports-optimisation-design.md.Implementations at
openkal-0.16.0: openkal-linux 0.17.0, openkal-macos 0.14.0, openkal-windows 0.12.0, openkal-emscripten 0.5.0, openkal-opensbi 0.8.3; above them openkal-musl 0.21.0 and openkal-llvm-runtime 0.15.5.