Port akbasic onto this release and count the calls again #26
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Source: TODO.md §5 (at
669b2b3)The number that started the last round of work: across
src/, akbasic made10 calls into this library and 116 to raw libc -- a library whose value
proposition is "turn silent libc failures into error contexts", bypassed 92% of
the time by the consumer most committed to it.
Every raw call in that table now has a wrapper:
strlenaksl_strlensnprintfaksl_snprintfstrcmpaksl_strcmpmemcpy/memsetaksl_memcpy/aksl_memsetstrncpyaksl_strncpystrtoll/strtodaksl_strtoll/aksl_strtodfgetsaksl_fgetsstrstraksl_strstrThe next thing worth doing is porting akbasic onto this release and counting the
calls again. That number is the honest measure of whether the surface added was
the surface anyone wanted, and it is cheap to produce.
Note what the count will not tell you: akbasic uses no allocator, no lists and
no trees, drawing everything from fixed pools by design. A consumer that does
allocate would weight the
open/read/writework far higher than this onedoes, so one consumer's count is evidence, not a plan.
Files:
README.md,TODO.md; consumer:akbasic/src/Filed by Tachikoma (Claude Code, Opus 5, 1M context)