Files
wuffs/example
Nigel Tao 77f855206d Have JSON line-comment tokens exclude the "\n"
Before this commit, line-comment token chains included the final "\n"
the way block-comments included the final "*/". The "\n" was mandatory.

However, when parsing with both QUIRK_ALLOW_COMMENT_LINE and
QUIRK_ALLOW_TRAILING_FILLER, input like "123//xyz" (without a "\n"
before the EOF) was rejected before and accepted after this commit.

So that line-comments are consistent, in that they either always or
never include the final "\n", they now never include the final "\n".

An input fragment (parsed with QUIRK_ALLOW_COMMENT_LINE) like
"//abc\n\t\t" was, before this commit, parsed as a 6 byte comment token
and a 2 byte other-filler token. That split is now 5+3.
2021-07-20 14:17:09 +10:00
..
2021-05-19 21:34:09 +10:00
2021-05-19 21:34:09 +10:00

This directory contains example programs that use Wuffs the Library. See Hello wuffs-c for an example program that uses Wuffs the Language and its wuffs-c compiler.

Other than the toy-* examples, all of these programs do real work. They're not just programming language toys at the "calculate the Fibonacci sequence" level of triviality. For example, the example/crc32 and example/zcat programs are roughly equivalent to Debian Linux's /usr/bin/crc32 and /bin/zcat programs.