I've made a mistake while creating thread and I think I'm no longer able to edit the title.
I'm from Poland, so such name is natural for us.
Euboea depends on POSIX and X86 highly, therefore I thought about Euboea like about another text processing / computation language to be used in shell scripts making programming easier.
> isn't interfacing with C and "no access to files" contradictory
As UNIX philosophy states, CLI tools may use stdin and stdout (among other streams), to read data, process it, and output it back. Also, this model is ensuring a) safety, b) simplicity.
Interfacing with C is actually not that advanced right now and all you can do is to specify C function name by modifying libE.c, it's exported name usable from Euboea and amount of parameters (-1 if vararg)
I'm from Poland, so such name is natural for us.
Euboea depends on POSIX and X86 highly, therefore I thought about Euboea like about another text processing / computation language to be used in shell scripts making programming easier.
> isn't interfacing with C and "no access to files" contradictory
As UNIX philosophy states, CLI tools may use stdin and stdout (among other streams), to read data, process it, and output it back. Also, this model is ensuring a) safety, b) simplicity.
Interfacing with C is actually not that advanced right now and all you can do is to specify C function name by modifying libE.c, it's exported name usable from Euboea and amount of parameters (-1 if vararg)