Funny programming language in snap! (Part 3)

Requests to the Community Collaborations
1

Continuing the discussion from Funny programming language in snap! (Part 2) - #100 by helicoptur.

Previous discussions:

2

I wonder if we're going to surpass the most-replied topic eventually?

3

haha ive seen a forum that went to part 5 or part 4

4

Yes, we might, but we have definitely secured a place in the leaderboard for a very long time.

5

yep

oh yeah, that's better.

6

the among us one?

7

yeah

8 
try start

break then if error //error reports if the command isn't recognized or the error

end
9

huh?

10

catch errors

anyway after the user writes the code, instead of a run button, we should just have the command

run
11

I think you guys have decided on the syntax, but how about actually coding it?

12

Wiki is the most replyed.

13

Technically it's not, the Among Us topics have like 5 parts to them, which means they're well over 100 more posts than the wiki topic.
The wiki topic is only the most replied because Administrative Categories doesn't have the 100 replies system.

14

Can anybody tell me the List syntax, I need it.

15

There isn't really a set-in-stone (agreed upon) syntax for lists afaik, but here are some suggestions I remember:

("item1",
 "item2",
 ("item1-nested",
  "item2-nested"))

["item1", "item2", ["item1-nested", "item2-nested"]]

{
"item1"
"item2"
{
"item1-nested"
"item2-nested"
}
}
16

i use

(item1, item2)
17

I like the second one.

Example
display text(what the user sees):

bagItems = ["Item 1", "Item 2",  pokemon = ["Charmander", "Pikachu"]]

Blocks(The Code translated to snap):

Numbers script pic
Numbers script pic828×132 15.7 KB
!

18

Also please forgive me because I keep using Pokemon as an example.

19

it's fine :slight_smile:

20

It's just that

  1. I like pokemon
  2. It is really practical for listing things instead of using Item 1, Item 2.(I might use Item 1, Item 2 sometimes.)