From: Johnny Richard <johnny@johnnyrichard.com>
To: ~johnnyrichard/olang-devel@lists.sr.ht
Cc: Johnny Richard <johnny@johnnyrichard.com>
Subject: [PATCH olang v4 0/4] Create --dump-tokens on compiler cli
Date: Mon, 19 Feb 2024 22:04:07 +0100 [thread overview]
Message-ID: <20240219210541.25624-1-johnny@johnnyrichard.com> (raw)
This patchset creates the lexer and a --dump-tokens functionality for
the compiler 0c.
Carlos Maniero (1):
lexer: test: add integration tests for --dump-tokens
Johnny Richard (3):
utils: create string_view data structure
lexer: create --dump-tokens cli command
docs: create man page for 0c compiler
.gitignore | 1 +
docs/Makefile | 21 ++-
docs/manpages/0c.md | 21 +++
examples/main_exit.0 | 3 +
src/0c.c | 129 +++++++++++++++++-
src/lexer.c | 235 +++++++++++++++++++++++++++++++++
src/lexer.h | 74 +++++++++++
src/string_view.c | 35 +++++
src/string_view.h | 34 +++++
tests/integration/cli_runner.c | 47 ++++++-
tests/integration/cli_runner.h | 3 +-
tests/integration/cli_test.c | 16 ++-
12 files changed, 604 insertions(+), 15 deletions(-)
create mode 100644 docs/manpages/0c.md
create mode 100644 examples/main_exit.0
create mode 100644 src/lexer.c
create mode 100644 src/lexer.h
create mode 100644 src/string_view.c
create mode 100644 src/string_view.h
--
2.43.2
next reply other threads:[~2024-02-19 20:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 21:04 Johnny Richard [this message]
2024-02-19 21:04 ` [PATCH olang v4 1/4] utils: create string_view data structure Johnny Richard
2024-02-19 21:04 ` [PATCH olang v4 2/4] lexer: create --dump-tokens cli command Johnny Richard
2024-02-19 21:04 ` [PATCH olang v4 3/4] docs: create man page for 0c compiler Johnny Richard
2024-02-19 21:04 ` [PATCH olang v4 4/4] lexer: test: add integration tests for --dump-tokens Johnny Richard
2024-02-19 20:07 ` [olang/patches/.build.yml] build failed builds.sr.ht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240219210541.25624-1-johnny@johnnyrichard.com \
--to=johnny@johnnyrichard.com \
--cc=~johnnyrichard/olang-devel@lists.sr.ht \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.johnnyrichard.com/olang.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox