* [olang/patches/.build.yml] build success
2024-02-22 18:24 [PATCH olang] build: rename 0c.c file to main.c Johnny Richard
@ 2024-02-22 17:26 ` builds.sr.ht
2024-02-27 2:18 ` [PATCH olang] build: rename 0c.c file to main.c Carlos Maniero
1 sibling, 0 replies; 3+ messages in thread
From: builds.sr.ht @ 2024-02-22 17:26 UTC (permalink / raw)
To: Johnny Richard; +Cc: ~johnnyrichard/olang-devel
olang/patches/.build.yml: SUCCESS in 37s
[build: rename 0c.c file to main.c][0] from [Johnny Richard][1]
[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/49745
[1]: mailto:johnny@johnnyrichard.com
✓ #1155591 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1155591
^ permalink raw reply [flat|nested] 3+ messages in thread
* [PATCH olang] build: rename 0c.c file to main.c
@ 2024-02-22 18:24 Johnny Richard
2024-02-22 17:26 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-02-27 2:18 ` [PATCH olang] build: rename 0c.c file to main.c Carlos Maniero
0 siblings, 2 replies; 3+ messages in thread
From: Johnny Richard @ 2024-02-22 18:24 UTC (permalink / raw)
To: ~johnnyrichard/olang-devel; +Cc: Johnny Richard
In order to make the source code easy to follow by someone who are not
involved on the development, we are renaming the 0c.c file (which is the
compiler main entrypoint) to main.c, so then anyone can guess what is
the role of this file.
Given that we still have a single executable in our code base, I think
it's fine to name the file as main.c.
Signed-off-by: Johnny Richard <johnny@johnnyrichard.com>
---
src/{0c.c => main.c} | 0
tests/unit/Makefile | 2 +-
2 files changed, 1 insertion(+), 1 deletion(-)
rename src/{0c.c => main.c} (100%)
diff --git a/src/0c.c b/src/main.c
similarity index 100%
rename from src/0c.c
rename to src/main.c
diff --git a/tests/unit/Makefile b/tests/unit/Makefile
index 7c6a8b3..498bf98 100644
--- a/tests/unit/Makefile
+++ b/tests/unit/Makefile
@@ -1,6 +1,6 @@
SRCS := $(wildcard *_test.c)
OBJS := $(patsubst %_test.c, %_test.o, $(SRCS))
-SUBJECT_OBJS := $(filter-out ../../build/0c.o, $(wildcard ../../build/*.o))
+SUBJECT_OBJS := $(filter-out ../../build/main.o, $(wildcard ../../build/*.o))
CFLAGS := -I../../src -I../shared
TESTS := $(patsubst %_test.c, %_test, $(SRCS))
EXEC_TESTS := $(patsubst %_test, ./%_test, $(TESTS))
--
2.43.2
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH olang] build: rename 0c.c file to main.c
2024-02-22 18:24 [PATCH olang] build: rename 0c.c file to main.c Johnny Richard
2024-02-22 17:26 ` [olang/patches/.build.yml] build success builds.sr.ht
@ 2024-02-27 2:18 ` Carlos Maniero
1 sibling, 0 replies; 3+ messages in thread
From: Carlos Maniero @ 2024-02-27 2:18 UTC (permalink / raw)
To: Johnny Richard, ~johnnyrichard/olang-devel
> Given that we still have a single executable in our code base, I think
> it's fine to name the file as main.c.
Agree that for now it works, but in the future I believe may split the
main.c into small programs. Like *cli/dump_tokens.c*, *cli/compiler.c*
and so on.
Aplied!
To git.sr.ht:~johnnyrichard/olang
60eacac..d12d495 main -> main
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2024-02-27 2:18 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-02-22 18:24 [PATCH olang] build: rename 0c.c file to main.c Johnny Richard
2024-02-22 17:26 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-02-27 2:18 ` [PATCH olang] build: rename 0c.c file to main.c Carlos Maniero
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