Cheddar

Cᴏɴᴏʀ O'Bʀɪᴇɴ

16:59

@Upgoat

Bálint

Cool feature for switches?

Cᴏɴᴏʀ O'Bʀɪᴇɴ

yeah, I have an idea

@Upgoat what are commas used for?

Upgoat

nothing yet

Cᴏɴᴏʀ O'Bʀɪᴇɴ

I've been out of the loop for a while. Does cheddar use semicolons?

Upgoat

@CᴏɴᴏʀO'Bʀɪᴇɴ they are optional

Cᴏɴᴏʀ O'Bʀɪᴇɴ

17:01

ok

Upgoat

semicolons are ugly imo

Bálint

@Upgoat ;/

Upgoat

:/

Cᴏɴᴏʀ O'Bʀɪᴇɴ

my idea is a "switch lambda"

Upgoat

elaborate? sounds interesting...

Cᴏɴᴏʀ O'Bʀɪᴇɴ

17:03

okay, so if you're not using commas for anything, then commas within a case statement could refer to multiple case values

Bálint

Maybe a branch-like switch in my opinion

Cᴏɴᴏʀ O'Bʀɪᴇɴ

switch value {
	case 0, 1: return 1
	else: return 2
}

(this is not a lambda)

Upgoat

@CᴏɴᴏʀO'Bʀɪᴇɴ oh, that's a good idea

Cᴏɴᴏʀ O'Bʀɪᴇɴ

(case word optional)

Upgoat

so you're using else instead of default?

ah, so switches are like a literal?

Cᴏɴᴏʀ O'Bʀɪᴇɴ

17:05

The above would be equivalently as a "switch lambda":

switch* v { 0, 1: 1; else: 2 }

which creates a function that can be called

Bálint

<object>->{
    <value1>:
        statement
    <value2>, <value3>:
        statement
}

Upgoat

should I make it then like: foo := switch* v { /* ... */ } or like c: switch* v { /* ... */ } foo

Cᴏɴᴏʀ O'Bʀɪᴇɴ

oh, hm

probably the former, so it can be anonymous

Bálint

So something like

Upgoat

switch -> "switch" "*"? <expression> "{"
    <case>
case -> ("case"|"default")? <expression> ":" <block> <case>
         "}"

nvm got it

Cᴏɴᴏʀ O'Bʀɪᴇɴ

17:09

Do you have a data entity?

Upgoat

no, I don't know what that is :|

Cᴏɴᴏʀ O'Bʀɪᴇɴ

a piece of information

Bálint

I meant something like

 myValue->{
         1:
             doThis()
         2, 3:
             doThat()
    }

Cᴏɴᴏʀ O'Bʀɪᴇɴ

there we go

Bálint

@CᴏɴᴏʀO'Bʀɪᴇɴ I tried

Cᴏɴᴏʀ O'Bʀɪᴇɴ

17:10

I think the -> arrow is already used

Upgoat

@Bálint that would be viewed as a lambda

Bálint

Then something else than arrow

Maybe ??

Upgoat

that would be confusing in writing though

Cᴏɴᴏʀ O'Bʀɪᴇɴ

yeah

Upgoat

> halp ?? is not wokring

Cᴏɴᴏʀ O'Bʀɪᴇɴ

17:13

I like switch simply because of the immediate knowledge one knows of its function

except to python programmers, but who cares about those :P

Upgoat

^ +1

Bálint

@Upgoat Then maybe actually star it :P

Upgoat

@Bálint actually I'll pin it

Bálint

BTW, the multiple value thing is technically possible in other languages as well

case1:
case2:
    statement;
    break;

Upgoat

yeah but no one likes breaks

Bálint

17:17

This way statement runs in bith cases

quartata

in Pytek, May 10 at 14:31, by El'endia Starman

I think we could possibly come up with a better system for that, not just switch statements. For instance, regarding code reuse, there are four kinds of "overlaps" I can think of: 1) overlap at the start, 2) overlap at the end, 3) one case's code is entirely within another, and 4) one case's end overlaps with another case's start.

in Pytek, May 10 at 14:37, by El'endia Starman

Oooh, I think the key ingredient would be to allow, explicitly, a way of executing multiple branches of a conditional (if/else or switch).

Bálint

@Upgoat If you do a traditional switch, then please just use brackets or simply make it only read it until it reaches the next ccase

quartata

in Pytek, May 12 at 23:48, by quartata

code = \input[SINGLEBYTE]();

tape = [0] * 2^16;
index = 0;

\for(instruction; code) {
  \switch(instruction) {
    "+": tape[index] += 1;
    "-": tape[index] -= 1;
    ">": index += 1;
    "<": index -= 1;
    ",": tape[index] = \getc[SINGLEBYTE]();
    ".": \print(char:tape[index]);
    "]": \hop(\find(code[\pos():0], "[")) \if tape[index];
    default: pass;
  }
}

in Pytek, May 12 at 23:51, by quartata

The switch statement syntax which I think is good

Upgoat

what is with all the \s

Cᴏɴᴏʀ O'Bʀɪᴇɴ

it's like (la)tex

Upgoat

17:20

:/ tex is markup not programming lang

Cᴏɴᴏʀ O'Bʀɪᴇɴ

idk

quartata

would everyone shut up about the backslashes for once

Bálint

@Upgoat Does cheddar have do...while loops?

quartata

anyways these were our thoughts on it

Upgoat

@Bálint planning on it

quartata

17:20

if anyone cares

Upgoat

gotta make normal fors work though

Cᴏɴᴏʀ O'Bʀɪᴇɴ

@quartata thanks

Upgoat

@quartata thanks for the input

quartata

This was the original syntax:

in Pytek, May 10 at 14:40, by El'endia Starman

\switchmulti[x](A){
    #A's start
}(A or B){
    #common code; A's end and B's start
}(B){
    #B's end
}

Upgoat

oh I got another idea, to put braces around the thing

quartata

17:22

Currently we're planning on doing it like this (I think):

\switch(x) {
  A: code
  A \or B: code
  B: code
}

Cᴏɴᴏʀ O'Bʀɪᴇɴ

that's decent

Bálint

@Upgoat Around the what?

Upgoat

switch foo {
    case bar {
        abc;
        def;
    }
}

quartata

I don't like the way that looks

Upgoat

D: okay

quartata

17:23

You have to keep in mind switch-case is for small things really

It's to be used sparingly in place of if-else

Bálint

4 mins ago, by Bálint

@Upgoat If you do a traditional switch, then please just use brackets or simply make it only read it until it reaches the next ccase

Upgoat

I coud allow braces+multline or :+singeline

that would inspire good practice

Cᴏɴᴏʀ O'Bʀɪᴇɴ

@quartata true

Upgoat

:D it works in JS

> switch(true) {
	case true: {
		console.log("true");
	}
}
[Log] true

Bálint

@Upgoat works in JS:

{
    <statement>
}

It's called scoping

quartata

17:24

@Bálint Yeah, anonymous block. Lots of languages have that. I personally like them

Bálint

@quartata I know, but some languages name it that

Upgoat

switch -> "switch" "*"? <expression> "{"
    <case>
case -> ("case" | "default")? <expression> <case_block> <case>
        "}"
case_block -> "{" <code_block> "}"
              ":" <statement>

@Bálint i know

Cᴏɴᴏʀ O'Bʀɪᴇɴ

you may get stars for your hideous work in TNB, but here you're amongst JS programmers.

Upgoat

@quartata except in ES6

Cᴏɴᴏʀ O'Bʀɪᴇɴ

^

quartata

17:25

@Upgoat except it still doesn't make a new scope in es6 you have to use let

Upgoat

→ 2 messages moved to Trash

Cᴏɴᴏʀ O'Bʀɪᴇɴ

{
  let a = 3;
}
a; // ReferenceError: a is not defined

Upgoat

removed blasphemy

^^ :D

Cᴏɴᴏʀ O'Bʀɪᴇɴ

@quartata because var declares a variable in the window.

quartata

@CᴏɴᴏʀO'Bʀɪᴇɴ which is disgusting

anyways

you already know this

Bálint

17:26

@quartata You could interpret it as JS having more feature

Cᴏɴᴏʀ O'Bʀɪᴇɴ

@quartata global variables have their place.

Upgoat

@quartata which is why I'm advocating use of babel

Bálint

@CᴏɴᴏʀO'Bʀɪᴇɴ I don't think so

var doesn't declare a global variable

Cᴏɴᴏʀ O'Bʀɪᴇɴ

@Bálint It declares a variable to the window.

quartata

Yeah, it's local in a function

Upgoat

17:28

though declaring scopes is bad practice as it's slow and confusing so I kinda understand why JS did it

quartata

@Upgoat kek

Cᴏɴᴏʀ O'Bʀɪᴇɴ

> let a = 3;
< undefined
> window.a;
< undefined
> var b = 3;
< undefined
> window.b;
< 3

Upgoat

@CᴏɴᴏʀO'Bʀɪᴇɴ :| does your browser not support let

oh wait nvm

Cᴏɴᴏʀ O'Bʀɪᴇɴ

it does

the window, remember

same thing with globals in node

Upgoat

huh TIL

Bálint

17:29

@CᴏɴᴏʀO'Bʀɪᴇɴ Only if you use it in the global scope

Cᴏɴᴏʀ O'Bʀɪᴇɴ

@Bálint That's only what I'm talking about.

var serves its purpose when you want to manipulate a variable given its name without using eval.

Bálint

@CᴏɴᴏʀO'Bʀɪᴇɴ BTW, the window object is the global scope

window.innerWidth = innerWidth

Cᴏɴᴏʀ O'Bʀɪᴇɴ

No, it isn't. Don't abuse bold.

Bálint

window.eval = eval

Cᴏɴᴏʀ O'Bʀɪᴇɴ

a can be accessed globally, but isn't in window.

did you read the code snippet...?

Upgoat

17:31

cheddar> var a := 5
cheddar> if a == 4 { print "Cheese is borked" } else { print "Nope" }
Cheese is borked

ono

zʏᴀʙiɴ101

@Upgoat Did you try a != 5?

as the condition

Upgoat

idk 5 == 4 works, something with the referencing

Bálint

@Upgoat As a windows user, how can I get a cheddar interpreter/compiler/I don't know

Upgoat

@Bálint cheddar.vihan.org

zʏᴀʙiɴ101

@Upgoat Can I file this issue?

Cᴏɴᴏʀ O'Bʀɪᴇɴ

17:34

I use windows and I still don't know

Upgoat

then go to the windows downloads

@zʏᴀʙiɴ101 ok, sure

Cᴏɴᴏʀ O'Bʀɪᴇɴ

@zʏᴀʙiɴ101 we're aware of the problem, there is no point in posting an issue

Upgoat

though I really need to fix Cheddar's GH... my git workflow is messed up

but that would requre me to either A) reset all commit history B) live with shit commit messages

Bálint

@Upgoat Done, now what?

Upgoat

did the installation script work?

Bálint

17:36

It started, then stopped immedialitely

@Upgoat Wait, does it need node?

Upgoat

yeah

@CᴏɴᴏʀO'Bʀɪᴇɴ do you know if can MSI installers do HTTP requests?

Cᴏɴᴏʀ O'Bʀɪᴇɴ

¯\_(ツ)_/¯

Never wrote one

Upgoat

can you write one for cheddar :3 :3 :3

Cᴏɴᴏʀ O'Bʀɪᴇɴ

I don't know how :P

Upgoat

I dont have windows so I cant do it either ;-;

zʏᴀʙiɴ101

17:39

Maybe a NSIS installer?

Cᴏɴᴏʀ O'Bʀɪᴇɴ

I'll look into it

Upgoat

idk what the difference is

i can make pkg installer for make though

Bálint

@Upgoat Now I have node, but still stops immedialitely

Upgoat

okay, do you have npm?

Bálint

@Upgoat Yup

That comes with node

Upgoat

17:41

okay. Try doing: git clone http://github.com/cheddar-lang/Cheddar.git

Bálint

@Upgoat Done

Upgoat

okay, now CD to the created Cheddar dir

then run npm install

Bálint

> Jade has been renamed to pug

That's the worst renaming I've seen in a while

Cᴏɴᴏʀ O'Bʀɪᴇɴ

^

Bálint

If cheddar is node-based, then why the hell did you use babel?

And install is done

Cᴏɴᴏʀ O'Bʀɪᴇɴ

17:49

babel-node

Bálint

@CᴏɴᴏʀO'Bʀɪᴇɴ Node supports ES6

So, now what?

Cᴏɴᴏʀ O'Bʀɪᴇɴ

the goat likes to think that not all of es6 is supported

Bálint

@Upgoat Installation is done, now what?

Upgoat

okay, check if a dist directory is there

Bálint

Where?

Yes there is

Upgoat

18:07

Okay good

npw run....

node.exe ./dist/cli/repl.js

Fatalize

Still not done is it?

Upgoat

No I ate all the cheese so now I have to wait for new

Fatalize

I remember a couple of weeks ago

"I'm almost done" - Upgoat

Upgoat

:|

i don't know what your taking about

Fatalize

oh you know

Upgoat

18:12

._.

Bálint

@Upgoat referenceError: dist is not defined

Upgoat

Wat

is that node error or bash error

Bálint

node error

Upgoat

Shit

Cantou

Bálint

at repl:1:1

repl.js:262:27

Upgoat

18:15

Wat

@Bálint can you post that as an issue to GH and describe the errors your getting etc.?

Bálint

Wait, I done it

I simply entered the command node D:\Cheddar\dist\cli\repl.js

and it works now

Now, how do I interpret a cheddar code

@Upg

Upgoat

:D

dies REPL show up?

Bálint

I get a yellow cheddar>

Upgoat

:D it's eitking

* working

just enter cheddar code and hit enter to run it

Bálint

@Upgoat That was not even close...

Symbol(KEY_NOT_FOUND)

:DDDD

It works!

I'm officially a cheddarian!

Upgoat

18:24

😄😄😄😄😄😄😄

Bálint

But is there a way, to use a separate file?

Upgoat

Yeah

instead of repl.js use prog.js

Bálint

@Upgoat How?

Upgoat

like:

node D:\Cheddar\dist\cli\prog.js myfile.cdr

Bálint

Nothing

Upgoat

18:54

D:

try using the git shell

Upgoat

19:22

@Bálint maybe try using node D:\Cheddar\dist\cli\cheddar.js < myfile.cdr

Upgoat

22:19

Cheddar's Switch (lambda?) Proposal! If you'd like to comment, suggest a change or anything, feel free to leave a comment, or if you have edit access, edit the proposal (but leave a footnote describing your changes)

4

Transcript for