<ScratchLang()> - Scratch as a Text-Based Programming Language || Open-Source

ISTILLMAKESTUFF

ThatCoder77471 wrote:
NOOOOOOOOOO!
https://github.com/scratchyone/ScratchLang

It must hurt bad, all that work!

ThatCoder77471

ISTILLMAKESTUFF wrote:
ThatCoder77471 wrote:
NOOOOOOOOOO!
https://github.com/scratchyone/ScratchLang
It must hurt bad, all that work!

After closer examination of this guys code, this guy apparently had the same idea as us. Scratch as a text-based programming language.
Good thing the last commit was 8 months ago, they don't seem to be working on it anymore.

I don't think a name change is necessary.

ThatCoder77471

bump

ThatCoder77471

After I'm done with the decompiler, I'll probably make a version of ScratchLang that will be ran in Scratch. Don't ask why.

Maybe if the compiler gets done I'll make ScratchLang in ScratchLang because why not.

ThatCoder77471

The decompiler can sort-of decompiler repeat an forever blocks. very buggy though.

Redstone1080

ThatCoder77471 wrote:
(#45)
The decompiler can sort-of decompiler repeat an forever blocks. very buggy though.

what are the bugs? maybe when i have spare time i can help out?

ThatCoder77471

Redstone1080 wrote:
ThatCoder77471 wrote:
(#45)
The decompiler can sort-of decompiler repeat an forever blocks. very buggy though.
what are the bugs? maybe when i have spare time i can help out?

For some reason, the blocks inside the repeat blocks are stored in a completely different place, which is bad for the decompiler because it reads the json left to right, up to down. It causes blocks on the bottom of the repeat to be on the inside.

I think I have an idea on how to fix it.

Last edited by ThatCoder77471 (Sept. 26, 2022 22:44:16)

Redstone1080

ThatCoder77471 wrote:
(#47)
Redstone1080 wrote:
ThatCoder77471 wrote:
(#45)
The decompiler can sort-of decompiler repeat an forever blocks. very buggy though.
what are the bugs? maybe when i have spare time i can help out?
For some reason, the blocks inside the repeat blocks are stored in a completely different place, which is bad for the decompiler because it reads the json left to right, up to down. It causes blocks on the bottom of the repeat to be on the inside.

I think I have an idea on how to fix it.

Maybe you need to remake the parser. A ScratchLang Decompiler V2 (SLDC2)?

ThatCoder77471

monkeh

ThatCoder77471

bump

ThatCoder77471

700 views and only 2 people are helping

good ig

i was kinda expecting more people to help

keep in mind that i don't care what language you use to program. If you want to make a compiler for python, fine. if you want to make a decompiler in c, fine. It gives people lots of options.

Last edited by ThatCoder77471 (Sept. 27, 2022 16:58:07)

mybearworld

ThatCoder77471 wrote:
(#51)
700 views and only 2 people are helping

good ig

i was kinda expecting more people to help

keep in mind that i don't care what language you use to program. If you want to make a compiler for python, fine. if you want to make a decompiler in c, fine. It gives people lots of options.

Is there some sort of specification? You currently have to either guess or read the bash, which is definetly inconvenient and may stop people from contributing.

ThatCoder77471

mybearworld wrote:
ThatCoder77471 wrote:
(#51)
700 views and only 2 people are helping

good ig

i was kinda expecting more people to help

keep in mind that i don't care what language you use to program. If you want to make a compiler for python, fine. if you want to make a decompiler in c, fine. It gives people lots of options.
You currently have to either guess or read the bash

wdym?

Redstone1080

ThatCoder77471 wrote:
(#53)
mybearworld wrote:
ThatCoder77471 wrote:
(#51)
keep in mind that i don't care what language you use to program. If you want to make a compiler for python, fine. if you want to make a decompiler in c, fine. It gives people lots of options.
You currently have to either guess or read the bash
wdym?

they mean that there's no universal document you can use to implement a decompiler. example: python language documentation is language-agnostic so you can implement python in any language you need/want to. for the scratchlang decompiler, it's not like that. you need to read the bash and see what it does, then implement that in whatever language/

ThatCoder77471

Redstone1080 wrote:
ThatCoder77471 wrote:
(#53)
mybearworld wrote:
ThatCoder77471 wrote:
(#51)
keep in mind that i don't care what language you use to program. If you want to make a compiler for python, fine. if you want to make a decompiler in c, fine. It gives people lots of options.
You currently have to either guess or read the bash
wdym?
they mean that there's no universal document you can use to implement a decompiler. example: python language documentation is language-agnostic so you can implement python in any language you need/want to. for the scratchlang decompiler, it's not like that. you need to read the bash and see what it does, then implement that in whatever language/

oh ok. i'll make comments in my shellscripts

Last edited by ThatCoder77471 (Sept. 28, 2022 01:52:30)

ThatCoder77471

Ok, V2 is officially working, and is way better than V1. It can decompiler repeat and forever blocks now! It just doesn't work if you have a c-block in a c-block though… Ima fix that soon tho

ThatCoder77471

found this, do you think it will be useful?

Redstone1080

ThatCoder77471 wrote:
(#57)
found this, do you think it will be useful?

It looks like it's made in JavaScript. Want me to make a JS port too?

ThatCoder77471

Redstone1080 wrote:
ThatCoder77471 wrote:
(#57)
found this, do you think it will be useful?
It looks like it's made in JavaScript. Want me to make a JS port too?

no. I don't want to give you any extra work

ThatCoder77471

c blocks in c blocks work now

Discuss Scratch