aplwc/tests/aplwc_errstr.c, branch memory-manager

The objects returned to the user are now integer-based references,

2026-08-31T19:44:56+00:00

not actual pointers. This means the aplwc internals can update those
pointers without the user noticing.

FossilOrigin-Name: 654c7d0ec85da295a7fb6ed381500410686b280f342fa81a30481f5e9a20c58a

Still a lot to be done, but I'm going to bed.

2026-08-30T20:52:43+00:00

Two remaining big issues:
* aplwc (the parameter passed "everywhere") - should it move or not?
* values returned from the public API should not move.

FossilOrigin-Name: 31ab3154b8f3d5ac167218496e9e204324bf0ac9d36b7bada8fe2a6c8f93d51c

Remove APLWC_MIN_MEM constant, and APLWC_MEM environment variable

2026-08-30T13:34:36+00:00

FossilOrigin-Name: affcf2ab9c573820c77778abfb4769fad8a30ce457411b02a9528470994c7a6b

Start working on the scanner.

2026-08-21T10:55:30+00:00

For now, all that is implemented is some functionality which imports UTF-8 into the
memory managed by aplwc, after checking that the data is in fact valid UTF-8.

FossilOrigin-Name: c861e88777d8180cb7b37c11fc7016a900f9d5821a7e3c8e8aab54118d2fca94

Get full coverage of aplwc-repl.

2026-08-20T20:54:43+00:00

This required wrapping malloc so that it can fail under our control.

FossilOrigin-Name: a27ccb5f02994393a518419bae15fd26ff0016c734d96350ae2137a1d3c0937c

Test the aplwc_errstr and aplwc_errstr_rc functions

2026-08-20T16:33:48+00:00

FossilOrigin-Name: c72c226a392ac25e688b131070bdfb2902b2a697766ecdfc0865b356cd3c2b2a