Private
Public Access
docs(twitter): add 1939170419958816855 corpus (NOTimothyLottes python-as-C-preprocessor + runtime code-gen)
4-post thread with @mmalex + @seflless, June 2025. @mmalex vibed-coded a python C preprocessor: finds /* python <code> */ in .c, runs the python, dumps stdout after the comment, replaces old block on change. @seflless points out Cog (https://cog.readthedocs.io) which did the same back in 2000ish. NOTimothyLottes: 'Many of my forth-like languages worked via nested runtime code gen, so it was possible to generate+run code to build either code or data, then repeat. The system would bootstrap its own assembler that way.' Precursor to the Jul 2026 micro macro-forth + nasm-bootstrapped 4KiB Linux Forth threads.
This commit is contained in:
@@ -0,0 +1,31 @@
|
|||||||
|
---
|
||||||
|
title: "@mmalex @seflless Many of my forth-like languages worked via nested runtime code"
|
||||||
|
author: "NOTimothyLottes"
|
||||||
|
handle: "@NOTimothyLottes"
|
||||||
|
post_url: "https://x.com/NOTimothyLottes/status/1939170419958816855"
|
||||||
|
post_id: "1939170419958816855"
|
||||||
|
timestamp: "2025-06-29 03:53:50"
|
||||||
|
post_count: 4
|
||||||
|
reply_count: 0
|
||||||
|
repost_count: 0
|
||||||
|
like_count: 2
|
||||||
|
view_count: 253
|
||||||
|
---
|
||||||
|
|
||||||
|
# @NOTimothyLottes — @mmalex @seflless Many of my forth-like languages worked via nested runtime code
|
||||||
|
|
||||||
|
## Post 1 (2025-06-28 20:01:01)
|
||||||
|
|
||||||
|
i vibe coded something horrendous and I love it: a python c preprocessor that finds blocks like /* python <arbitrary python code> */ in a .c file, runs the python, and dumps the stdout after the comment, replacing any old block if needed. im using it to precompute tables...
|
||||||
|
|
||||||
|
## Post 2 (2025-06-28 21:27:35) — reply to Post 1
|
||||||
|
|
||||||
|
@mmalex There was a python tool for this remember as far back as 2000ish when working on a large c/c++ game codebase. Ah found it, it’s called Cog: https://cog.readthedocs.io/en/latest/
|
||||||
|
|
||||||
|
## Post 3 (2025-06-28 23:03:41) — reply to Post 2
|
||||||
|
|
||||||
|
@seflless ah yes ! I knew it existed - it wasnt an original idea after all, but like a faint memory stirring in my brain - but couldn't find it. thanks for the link!
|
||||||
|
|
||||||
|
## Post 4 (2025-06-29 03:53:50) — reply to Post 3
|
||||||
|
|
||||||
|
@mmalex @seflless Many of my forth-like languages worked via nested runtime code gen, so it was possible to generate+run code to build either code or data, then repeat. The system would bootstrap its own assembler/etc that way.
|
||||||
@@ -0,0 +1,70 @@
|
|||||||
|
{
|
||||||
|
"root_post_id": "1939170419958816855",
|
||||||
|
"posts": [
|
||||||
|
{
|
||||||
|
"post_id": "1939051429060018590",
|
||||||
|
"author": "𝖒𝖒𝖆𝖑𝖊𝖝",
|
||||||
|
"handle": "mmalex",
|
||||||
|
"text": "i vibe coded something horrendous and I love it: a python c preprocessor that finds blocks like /* python <arbitrary python code> */ in a .c file, runs the python, and dumps the stdout after the comment, replacing any old block if needed. im using it to precompute tables...",
|
||||||
|
"timestamp": "2025-06-28 20:01:01",
|
||||||
|
"media_urls": [],
|
||||||
|
"reply_to_id": null,
|
||||||
|
"quote_of_id": null,
|
||||||
|
"metrics": {
|
||||||
|
"reply_count": 11,
|
||||||
|
"repost_count": 2,
|
||||||
|
"like_count": 65,
|
||||||
|
"view_count": 14910
|
||||||
|
}
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"post_id": "1939073216628068762",
|
||||||
|
"author": "Francois Laberge",
|
||||||
|
"handle": "seflless",
|
||||||
|
"text": "@mmalex There was a python tool for this remember as far back as 2000ish when working on a large c/c++ game codebase. Ah found it, it’s called Cog: https://cog.readthedocs.io/en/latest/",
|
||||||
|
"timestamp": "2025-06-28 21:27:35",
|
||||||
|
"media_urls": [],
|
||||||
|
"reply_to_id": "1939051429060018590",
|
||||||
|
"quote_of_id": null,
|
||||||
|
"metrics": {
|
||||||
|
"reply_count": 2,
|
||||||
|
"repost_count": 0,
|
||||||
|
"like_count": 4,
|
||||||
|
"view_count": 641
|
||||||
|
}
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"post_id": "1939097400183763189",
|
||||||
|
"author": "𝖒𝖒𝖆𝖑𝖊𝖝",
|
||||||
|
"handle": "mmalex",
|
||||||
|
"text": "@seflless ah yes ! I knew it existed - it wasnt an original idea after all, but like a faint memory stirring in my brain - but couldn't find it. thanks for the link!",
|
||||||
|
"timestamp": "2025-06-28 23:03:41",
|
||||||
|
"media_urls": [],
|
||||||
|
"reply_to_id": "1939073216628068762",
|
||||||
|
"quote_of_id": null,
|
||||||
|
"metrics": {
|
||||||
|
"reply_count": 2,
|
||||||
|
"repost_count": 0,
|
||||||
|
"like_count": 0,
|
||||||
|
"view_count": 734
|
||||||
|
}
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"post_id": "1939170419958816855",
|
||||||
|
"author": "NOTimothyLottes",
|
||||||
|
"handle": "NOTimothyLottes",
|
||||||
|
"text": "@mmalex @seflless Many of my forth-like languages worked via nested runtime code gen, so it was possible to generate+run code to build either code or data, then repeat. The system would bootstrap its own assembler/etc that way.",
|
||||||
|
"timestamp": "2025-06-29 03:53:50",
|
||||||
|
"media_urls": [],
|
||||||
|
"reply_to_id": "1939097400183763189",
|
||||||
|
"quote_of_id": null,
|
||||||
|
"metrics": {
|
||||||
|
"reply_count": 0,
|
||||||
|
"repost_count": 0,
|
||||||
|
"like_count": 2,
|
||||||
|
"view_count": 253
|
||||||
|
}
|
||||||
|
}
|
||||||
|
],
|
||||||
|
"source_url": "https://x.com/NOTimothyLottes/status/1939170419958816855"
|
||||||
|
}
|
||||||
Reference in New Issue
Block a user