Open matijapretnar opened 8 years ago
A separate branch, one per language.
I understand you want to keep master
clean, but I don't want to have a dozen of inactive branches in the repository. So, whoever is interested in porting any of the languages can message me and I will be happy to send them the files. I'll also rename this issue to attract anyone interested.
It would be better to have one issue per language, so you we can close them, and perhaps organize them into a milestone.
Oh, and then I could just attach a ZIP with the source code to each issue!
Hi, thank you for this great repository. I enjoyed it very much as a learning resource!
May I suggest a separate repository plzoo-staging for the half-baked languages (instead of branches or zips)? I think that could also attract contributions.
What's the point of a separate repository? It'll just become obsolete. I still think the best way is to just fork this repository, add a language (half baked or not), and then merge it once it's ready.
We still have some other languages in various stages of development laying around:
calc+var
(which I guess is an older version ofcalc_var
, but I did not look exactly where it diverged)comm
(a simple imperative language)commar
(a simple imperative language with arrays)dat
(mini SQL)minicalc
(again it looks like an older version ofcalc
)minimlcatch
(looks likeminiml_error
plus error handling)minimlp
(miniml
with pairs)minscheme
(mini Scheme - withoutcallcc
)ob
(looks like an older version ofboa
)ulc
(looks like an older version oflambda
)These languages are not mature enough to put in plzoo, but could be a useful starting point for future contributions, so I would make them public. Where would be an appropriate place to put them? A subfolder, a separate branch?