HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
asrp
flpc
Forth2018–2021
asrp / flpc

flpc

Forth Lisp Python Continuum: A small highly dynamic self-bootstrapping language

7Distinct people
8Mentions
0Explicit recommenders
226GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Forth Lisp Python Continuum: A small highly dynamic self-bootstrapping language

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 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 12:56:33 AM 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 year8 dated mentions

Observed mentions: 2018-02-13 19:36:57 UTC to 2021-11-18 03:24:30 UTC.

012342018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 2 mentions; 2 submissions, 0 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2021

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC220
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC413
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC202

What Hacker News says

4 sources
But why? I don't see that the author explains why he doesn't use what's already in the language which he uses to implement all his "dictionaries": https://docs.python.org/3/tutorial/datastructures.html#dicti... Also, the "improvement" is when starting from "a linear search through all of keys"? Edit: Thanks to anonymoushn, so the language in which the "dictionaries" are implemented is actually an independent language: "Almost all of Flpc is written in Flpc itself and defined at runtime. This means almost everything is modifiable at runtime using rebind: including the loop for reading input, compiling functions, looking up names and rebind: itself!" From: https://github.com/asrp/flpc
In Speed improvements using hash tables
> Those languages have nothing in common other than being pleasant to work with.. That's where the author had an insight, that they (could) have everything in common - except for the syntax on a surface level. Underneath, languages are just different ways to produce and operate on the same "stuff", data and algorithms - values, function, list, dictionary, stack. So, to me it makes sense that there can be a Lisp-y flavor of Python, Pythonic flavor of Lisp, Forthy Python, and so on. It's a matter of parsing/compiling them into a common format, targeting the same interpreter or virtual machine. That said, this Forth-Lisp-Python Continuum verges on mad genius, to have all these different syntaxes in one language. It was interesting to see this project, since I've been working on a hobby language, whose syntax is infix-oriented like C (but eve
Read the rest
rything is an expression). It gets parsed into a prefix-oriented Lisp-like syntax tree. The interpreter is a "machine" based on Lisp's eval, with lambda, macro, tail-call optimization, etc. So, basically, the language is just syntactic sugar that compiles down to whatever the machine expects. I plan to implement another (much simpler) parser for a Lisp-flavor of the same language. In the case of FLPContinuum, I see that the interpreter is a stack-based loop (https://github.com/asrp/flpc/blob/f47de76fcab6d2d2b1840e5376...). The actual implementation of the "machine" almost doesn't matter for the language(s) though, as long as the interface stays the same.
In Forth Lisp Python Continuum: A small highly-dynamic self-bootstrapping language

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.