@Helen0903 Pulled.
Saved me a lot of confusion later on
It's released
@DennisMitchell Can we change DOBELA implementation to this one? Old asm interpreter doesn't follow the spec
in some cases, which has bitten me once already. I believe new implementation is better in many respects, including maintainability, following the spec and
handling many corner cases which dobelx64 doesn't. Currently DOBELA answers exist only in Hello World and Add a language to a polyglot threads.
Changing the interpreter will break several old polyglot answers (207-210, all of them are mine) and the program provided in the comments of Hello World answer.
All these breakages are due to dobelx64 not following the spec. If this is a problem I can fix all those answers for new interpreter, but I see no point in doing this.
If that is fine, I'll write a pull request.
in some cases, which has bitten me once already. I believe new implementation is better in many respects, including maintainability, following the spec and
handling many corner cases which dobelx64 doesn't. Currently DOBELA answers exist only in Hello World and Add a language to a polyglot threads.
Changing the interpreter will break several old polyglot answers (207-210, all of them are mine) and the program provided in the comments of Hello World answer.
All these breakages are due to dobelx64 not following the spec. If this is a problem I can fix all those answers for new interpreter, but I see no point in doing this.
If that is fine, I'll write a pull request.
This example does not typecheck due to old compiler impl
@ice1000 I'll have to update to Fedora 30 to update Agda (so it will take a while), but even Fedora 30 is still on Agda 2.5.4. When was Adga 2.6 released?
@DennisMitchell No, dobelx64 behaves strangely due to bug(s?), not because it deliberately deviates from spec. The author of dobelx64 is actually the one who wrote the spec.
Now that I think of it, dobelx64 has some value of being a "classical" implementation, so it's better to keep it. I will write a PR today or tomorrow.
Now that I think of it, dobelx64 has some value of being a "classical" implementation, so it's better to keep it. I will write a PR today or tomorrow.
Suggestion for a programming language: the esolang UBFIM (https://esolangs.org/wiki/Ultimate_bf_instruction_minimalization!). The only current interpreter there is is one wrote in Basic (https://esolangs.org/wiki/UBFIM_interpreter) so it'd be useful to have it on here
(if you want to add it, friend me on Discord (i'm more active there, and probably won't get notifs here), my tag is
RailRunner16#7053)
i can send you a link @DennisMitchell (if you want)
(namely the additions of bitwise shifting functions, removal of parens from while statements and the addition of the chomp$ function)
Thx dennis if you do put it on the site
@DennisMitchell I have a language, it's called 32. Can you guys please add it. The "Hello, World!" program is either
IU or "Hello, World!"U. It uses Python as it's parent language.
@DennisMitchell I also have a language called StupidStackLanguage, the hello world program is as follows:
aviiiaiglbmfavdaiiiglbmlblbgifviiffiiifavdaviiimfaiiimwwifbbbbbfiiifwdfwdddfbvfbbThere is a python interpreter on the wiki page
thanks!
hey @DennisMitchell just to keep you in the know, there have been some major updates concerning Caboose, if you could update it to master (I overwrote the old code with the latest version, which is v2) that would be great :)
I can help with any setup needed and since there's a package manager coming out soon for it i can help you with setting that up as well when its ready :)
FYI Caboose v2 is still indev, I have just a couple of things to add then the basics will be complete, and I can notify you of updates to the completed lang
@DennisMitchell you should add Argh! Its interpreter is in javascript and is available at http://argh.sha-bang.de/
Team, may I kindly request to consider including jtc (json parser tool - https://github.com/ldn-softdev/jtc) in TIO?