HZhzhou321·Sep 30, 2026Submission
1 points · Open discussionhzhou
MyDef
HTML2015–2026
hzhou / MyDef
MyDef
Programming in the next paradigm -- your way
6Distinct people
12Mentions
0Explicit recommenders
52GitHub stars
What to know before exploring
What it is
Programming in the next paradigm -- your way
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year12 dated mentions
Observed mentions: 2015-03-06 10:17:04 UTC to 2026-09-30 20:16:17 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 4 | 1 | 3 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
12 sourcesFor those who are interested, checkout MyDef - https://github.com/hzhou/MyDef
In Programming breakthroughs we needMyDef – Programming in the next paradigm – your way
2 points · Open discussionNot sure about the example semantics, but with MyDef (https://github.com/hzhou/MyDef), it is trivial --
$call value_ops, val, operate, operate
subcode: value_ops(v, @ops)
type_t $(v) = allocate();
$(for:op in $(ops))
type_t tmp$(_i) = operate($(v));
$(set-1:v=tmp$(_i))
destroy($(v))
MyDef is a general purpose preprocessor.
EDIT: maybe this is more fit what was intended
type_t var;
$(for:op in allocate, operate, operate, destroy)
var = $(op)(var);
In Show HN: C programming language extension: Cedro pre-processor> Writing the code out-of-order is the whole point.
Yes!
MyDef, https://github.com/hzhou/MyDef, is such a system.
In Donald Knuth was framedAnother one, geared toward taking repetition and verbosity out of programming:
https://github.com/hzhou/MyDef
https://htmlpreview.github.io/?https://github.com/hzhou/MyDe...
In GPP – general-purpose preprocessorThis seems to be the Github repository for it: https://github.com/hzhou/MyDef
In Sadly, I must say goodbye to Leaf, my programming languageI use MyDef to achieve most of features `cpy` is trying to introduce:
# t.def
page: t, basic_frame
module: c
a=10
b=a
$dump a, b
$ mydef_run t.def
PAGE: t
--> [./t.c]
gcc -std=c99 -O2 -o./t ./t.c && ./t
:a=10, b=10
I didn't introduce `known` keyword. If I want straight C code passthrough I simply append semicolons.
MyDef is a general preprocessor, so I need the page and module declarations to tell what file and types I am generating. It always shows the command it actually runs, so there is no magic. And it does not pretend to replace C. It always produces `.c` file for debugging or merging with existing workflow.
As long as MyDef is strictly preprocessor, it is purely complementary. If you prefer straight C/C++ at places, just use straight C. If you have questions on w
Read the rest
hat MyDef syntax does, just read the C output.
It does pose some restrictions on the C I write. I do not write long statements in multiple lines and rely on my editor to softwrap the lines. Long lines are difficult to read anyway with or without splitting and soft-wrapped lines are not much difficult to read anyway. I often can avoid long lines by refactoring. In rare cases that lines still end up too long, I leave it as is to remind me that it needs further work.
Sometimes I need import third-party raw c code during a progress of refactoring or code digesting. MyDef has template construct to quote them directly.
MyDef: https://github.com/hzhou/MyDef
output_c: https://github.com/hzhou/output_c
Sounds similar to MyDef: https://github.com/hzhou/MyDef. However, MyDef doesn't attempt to be a new language, it attempts to be meta-layer. With MyDef you can save time with boilerplate, and more importantly, reorganize code into a better semantical structure.
In Ask HN: Have you created a programming language and why?The preprocessor reminds me a bit MyDef:
https://github.com/hzhou/MyDef
In Mu: making programs easier to understand in the largeMyDef – a layer on top of your programming language
1 points · Open discussion