expose `stdin` and `stdout`

[thacuber2a03]

expose `stdin` and `stdout`

[vtereshkov]

Done.

Piping example:

// test.um
import "std.um"

fn main() {
	a := make([]char, 100000)
	std.fread(std.stdin(), &a)
	std.fwrite(std.stdout(), []char("PATH = " + str(a)))
}

C:\Users\vtere\Desktop\umka-lang\umka_windows_mingw>echo %path% | umka.exe ..\test.um
PATH = C:\emsdk;C:\emsdk\upstream\emscripten;C:\emsdk\node\14.18.2_64bit\bin;...

[thacuber2a03]

YEEEEEEEEAHHHHHH

[thacuber2a03]

wait but why are they exposed as functions?

[vtereshkov]

@thacuber2a03 Because I don't want to allow users to rewrite built-in variables.

[thacuber2a03]

@thacuber2a03 Because I don't want to allow users to rewrite built-in variables.

why can you assign to module variables? that doesn't make sense to me

[vtereshkov]

@thacuber2a03 In Umka, you can assign to any variable (that's why they are called variables). There is no such concept as non-assignable variables, because I cannot imagine many use cases for them. So stdin etc. can be either constants or functions.

[thacuber2a03]

I meant, like, in most programming languages you can't change the variables of another module without exporting them
and speaking of constants, can't the file pointers just be that then?

[vtereshkov]

in most programming languages you can't change the variables of another module without exporting them

Of course you cannot. But then you cannot see them from other modules either. If you need stdin, you have to export it from std.um, but then you can re-assign it too.

[thacuber2a03]

@vtereshkov well, what about making them constants then?