in compiler i go simple thpugh im not saying this is final form of
language i just want to s\go for simple (most or almost most 'naked' from various decorators_ syntax and see how can it go

for example i now may compile such things

void draw
DrawSomeText2 0xffffff|0|160|"c1 %08x c2 %08x c3 %08x \x00"|c1|c2|c3
DrawSomeText2 0xffffff|0|170|"c4 %08x c5 %08x c6 %08x \x00"|c4|c5|c6
DrawSomeText2 0xffffff|0|180|"c7 %08x c8 %08x c9 %08x \x00"|c7|c8|c9
DrawSomeText2 0xffffff|0|190|"c10 %08x c11 %08x c12 %08x \x00"|c10|c11 c12
DrawSomeText2 0xffffff|10|220|"test aa %f \x00"|aa+=0.010101

;

void OnResize;

void main: RegisterRunFrame &RunFrame, RegisterMouseMove &ProcessMouseMove
RegisterKeyDown &ProcessKeyDown, RegisterOnResize &OnResize, SetSleepValue 30, SetScaleOnResize 1
SetupWindow3 " compiled by fir's furia proto c compiler \x00" 20 20 640 480 320 240 ;

the ; goes for return and | are optional
for if i temporarely use

last_key_pressed?=keyR: AddBackgrounColor 0x10 .

i mean dot is and end of if block (i think return and ending if should be different siggns possibly becouse tis is easily mistaken and makes well known compile errors when you got few }}}}}} at the end

hivever i kno if i use , as a log line spearators then possibly ; shpoul be made as an ifs block ends and . as a function end this way it would more resemble normal sentence - maybe i will change it for now i think i yet stay(becouse i got it this as i got and changing it now dont changes much) though in fact this is tempting, so maybe indeed, i wil change it

what else? a bit more on this later

wtorek, 10 maja 2022 o 14:20:31 UTC+2 fir napisał(a):
> in compiler i go simple thpugh im not saying this is final form of
> language i just want to s\go for simple (most or almost most 'naked' from various decorators_ syntax and see how can it go
>
> for example i now may compile such things
>
>
> void draw
> DrawSomeText2 0xffffff|0|160|"c1 %08x c2 %08x c3 %08x \x00"|c1|c2|c3
> DrawSomeText2 0xffffff|0|170|"c4 %08x c5 %08x c6 %08x \x00"|c4|c5|c6
> DrawSomeText2 0xffffff|0|180|"c7 %08x c8 %08x c9 %08x \x00"|c7|c8|c9
> DrawSomeText2 0xffffff|0|190|"c10 %08x c11 %08x c12 %08x \x00"|c10|c11 c12
> DrawSomeText2 0xffffff|10|220|"test aa %f \x00"|aa+=0.010101
>
> ;
>
> void OnResize;
>
> void main: RegisterRunFrame &RunFrame, RegisterMouseMove &ProcessMouseMove
> RegisterKeyDown &ProcessKeyDown, RegisterOnResize &OnResize, SetSleepValue 30, SetScaleOnResize 1
> SetupWindow3 " compiled by fir's furia proto c compiler \x00" 20 20 640 480 320 240 ;
>
> the ; goes for return and | are optional
> for if i temporarely use
>
> last_key_pressed?=keyR: AddBackgrounColor 0x10 .
>
> i mean dot is and end of if block (i think return and ending if should be different siggns possibly becouse tis is easily mistaken and makes well known compile errors when you got few }}}}}} at the end
>
> hivever i kno if i use , as a log line spearators then possibly ; shpoul be made as an ifs block ends and . as a function end this way it would more resemble normal sentence - maybe i will change it for now i think i yet stay(becouse i got it this as i got and changing it now dont changes much) though in fact this is tempting, so maybe indeed, i wil change it
>
> what else? a bit more on this later

i changed so now . is return and ; is loop and if end block
this sole dot is lookin weird though its standable imo

so this is for example legal

void OnResize:a?=2:doo;.
i could also use ; as for ending block
some could maybe say this void OnResize:a?=2:doo;; looks better
though i probbaly add yet now
void OnResize{a?=2{doo}}
as an optional for void OnResize:a?=2:doo;.
in this case } will check the nesting level and emit ret if not loop/if opened

i used a{3} as an initializer for int but the advantages of readiblity probably promote it here
for block use

wtorek, 10 maja 2022 o 15:25:27 UTC+2 fir napisał(a):
> wtorek, 10 maja 2022 o 14:20:31 UTC+2 fir napisał(a):
> > in compiler i go simple thpugh im not saying this is final form of
> > language i just want to s\go for simple (most or almost most 'naked' from various decorators_ syntax and see how can it go
> >
> > for example i now may compile such things
> >
> >
> > void draw
> > DrawSomeText2 0xffffff|0|160|"c1 %08x c2 %08x c3 %08x \x00"|c1|c2|c3
> > DrawSomeText2 0xffffff|0|170|"c4 %08x c5 %08x c6 %08x \x00"|c4|c5|c6
> > DrawSomeText2 0xffffff|0|180|"c7 %08x c8 %08x c9 %08x \x00"|c7|c8|c9
> > DrawSomeText2 0xffffff|0|190|"c10 %08x c11 %08x c12 %08x \x00"|c10|c11 c12
> > DrawSomeText2 0xffffff|10|220|"test aa %f \x00"|aa+=0.010101
> >
> > ;
> >
> > void OnResize;
> >
> > void main: RegisterRunFrame &RunFrame, RegisterMouseMove &ProcessMouseMove
> > RegisterKeyDown &ProcessKeyDown, RegisterOnResize &OnResize, SetSleepValue 30, SetScaleOnResize 1
> > SetupWindow3 " compiled by fir's furia proto c compiler \x00" 20 20 640 480 320 240 ;
> >
> > the ; goes for return and | are optional
> > for if i temporarely use
> >
> > last_key_pressed?=keyR: AddBackgrounColor 0x10 .
> >
> > i mean dot is and end of if block (i think return and ending if should be different siggns possibly becouse tis is easily mistaken and makes well known compile errors when you got few }}}}}} at the end
> >
> > hivever i kno if i use , as a log line spearators then possibly ; shpoul be made as an ifs block ends and . as a function end this way it would more resemble normal sentence - maybe i will change it for now i think i yet stay(becouse i got it this as i got and changing it now dont changes much) though in fact this is tempting, so maybe indeed, i wil change it
> >
> > what else? a bit more on this later
> i changed so now . is return and ; is loop and if end block
> this sole dot is lookin weird though its standable imo
>
> so this is for example legal
>
> void OnResize:a?=2:doo;.
> i could also use ; as for ending block
> some could maybe say this void OnResize:a?=2:doo;; looks better
> though i probbaly add yet now
> void OnResize{a?=2{doo}}
> as an optional for void OnResize:a?=2:doo;.
> in this case } will check the nesting level and emit ret if not loop/if opened
>
> i used a{3} as an initializer for int but the advantages of readiblity probably promote it here
> for block use

ok i added it accepts all 3 syntaxes now

void OnResize1:a?=2:doo;.
void OnResize2:a?=2:doo;;
void OnResize3{a?=2{doo}}

void OnResize.
void OnResize;
void OnResize{}

i think teh first ist most basic/fundamental but the third is liek to be more likely to see on,
also funni it seems those block parenthesis gat a feel of c, so liek they more responsible for it (as for surface things as for me c is more semantically inside, but hios surface also counts)

wtorek, 10 maja 2022 o 16:04:57 UTC+2 fir napisał(a):
>
> void OnResize1:a?=2:doo;.
> void OnResize2:a?=2:doo;;
> void OnResize3{a?=2{doo}}

compare it to standard c
void OnResize3(){if(a==2){doo;}}

its quite longer - 7 characters its quite a lot

where in my versiondoo may be both a variable or function call - if defined

wtorek, 10 maja 2022 o 16:25:44 UTC+2 fir napisał(a):
> wtorek, 10 maja 2022 o 16:04:57 UTC+2 fir napisał(a):
> >
> > void OnResize1:a?=2:doo;.
> > void OnResize2:a?=2:doo;;
> > void OnResize3{a?=2{doo}}
> compare it to standard c
> void OnResize3(){if(a==2){doo;}}
>
> its quite longer - 7 characters its quite a lot
>
> where in my versiondoo may be both a variable or function call - if defined

so for example this syntax is compiled

void ProcessKeyDown int last_key_pressed
{
.PAGE_UP=33
.keyR=0x52
.keyG=0x47
.keyB=0x42
last_key_pressed?=PAGE_UP{ToggleFullscreen}
last_key_pressed?=0x41{foo frame_size_x frame_size_y/2 3 4}
last_key_pressed?=0x53{foo 2|3|4|5,foo 6 7 8 9}
last_key_pressed?=0x43{MessageBoxA 0 "captionC\x00" "title\x00" 0}
last_key_pressed?=keyR{AddBackgrounColor 0x10} last_key_pressed?=keyG{AddBackgrounColor 0x1000}
last_key_pressed?=keyB{AddBackgrounColor 0x100000}
}

wtorek, 10 maja 2022 o 16:52:45 UTC+2 fir napisał(a):
> wtorek, 10 maja 2022 o 16:25:44 UTC+2 fir napisał(a):
> > wtorek, 10 maja 2022 o 16:04:57 UTC+2 fir napisał(a):
> > >
> > > void OnResize1:a?=2:doo;.
> > > void OnResize2:a?=2:doo;;
> > > void OnResize3{a?=2{doo}}
> > compare it to standard c
> > void OnResize3(){if(a==2){doo;}}
> >
> > its quite longer - 7 characters its quite a lot
> >
> > where in my versiondoo may be both a variable or function call - if defined
> so for example this syntax is compiled
>
>
> void ProcessKeyDown int last_key_pressed
> {
> .PAGE_UP=33
> .keyR=0x52
> .keyG=0x47
> .keyB=0x42
> last_key_pressed?=PAGE_UP{ToggleFullscreen}
> last_key_pressed?=0x41{foo frame_size_x frame_size_y/2 3 4}
> last_key_pressed?=0x53{foo 2|3|4|5,foo 6 7 8 9}
> last_key_pressed?=0x43{MessageBoxA 0 "captionC\x00" "title\x00" 0}
> last_key_pressed?=keyR{AddBackgrounColor 0x10} last_key_pressed?=keyG{AddBackgrounColor 0x1000}
> last_key_pressed?=keyB{AddBackgrounColor 0x100000}
> }

i added

void goo int z1 int z2 int z3 -> int z4 int z5 int z6
z4=z1+z2
z5=z2+z3
z6=z3+z1;

void doo {
a b c = goo 2 3 4,
printf " a %d b %d c %d \x00" a b c }

this is function retuirning many values (bit chaos mode but stoll) (later i will do that those ints can be skippd i guess
void goo z1 z2 z3 -> z4 z5 z6
z4=z1+z2
z5=z2+z3
z6=z3+z1;
this si becouse autodefining not known symbols as new ints seem to work ok as for the moment at least

On Tuesday, May 10, 2022 at 7:20:31 AM UTC-5, fir wrote:
> in compiler i go simple thpugh im not saying this is final form of
> language i just want to s\go for simple (most or almost most 'naked' from various decorators_ syntax and see how can it go
>
> for example i now may compile such things
>
>
> void draw
> DrawSomeText2 0xffffff|0|160|"c1 %08x c2 %08x c3 %08x \x00"|c1|c2|c3
> DrawSomeText2 0xffffff|0|170|"c4 %08x c5 %08x c6 %08x \x00"|c4|c5|c6
> DrawSomeText2 0xffffff|0|180|"c7 %08x c8 %08x c9 %08x \x00"|c7|c8|c9
> DrawSomeText2 0xffffff|0|190|"c10 %08x c11 %08x c12 %08x \x00"|c10|c11 c12
> DrawSomeText2 0xffffff|10|220|"test aa %f \x00"|aa+=0.010101
>
> ;

This has some similarities to the Logo language, an unparenthesized Lisp.
If all your functions (and/or operators) have a fixed arity, then you can
parse them straight up without needing any parens. This is actually the
original way Polish notation was done by the Polish guy himself.

poniedziałek, 16 maja 2022 o 04:54:31 UTC+2 luser droog napisał(a):
> On Tuesday, May 10, 2022 at 7:20:31 AM UTC-5, fir wrote:
> > in compiler i go simple thpugh im not saying this is final form of
> > language i just want to s\go for simple (most or almost most 'naked' from various decorators_ syntax and see how can it go
> >
> > for example i now may compile such things
> >
> >
> > void draw
> > DrawSomeText2 0xffffff|0|160|"c1 %08x c2 %08x c3 %08x \x00"|c1|c2|c3
> > DrawSomeText2 0xffffff|0|170|"c4 %08x c5 %08x c6 %08x \x00"|c4|c5|c6
> > DrawSomeText2 0xffffff|0|180|"c7 %08x c8 %08x c9 %08x \x00"|c7|c8|c9
> > DrawSomeText2 0xffffff|0|190|"c10 %08x c11 %08x c12 %08x \x00"|c10|c11 c12
> > DrawSomeText2 0xffffff|10|220|"test aa %f \x00"|aa+=0.010101
> >
> > ;
> This has some similarities to the Logo language, an unparenthesized Lisp.
> If all your functions (and/or operators) have a fixed arity, then you can
> parse them straight up without needing any parens. This is actually the
> original way Polish notation was done by the Polish guy himself.

this is not even a trick , i just use here newline as a separator, so the rule is just if first atom
is a function call (and if this is a functiob call i know becouse first scaning pass collected
definition names and import names) then this is a function call name and the all next atoms
are arguments

hovever this makes slight problem, too - i cant break arguments on newlines
foo arg1
arg2
arg3

(i would need to use some continue sign
foo arg1 \
arg2 \
arg3
which is not so good, and if not use continue sign i would need to denotoe end of arguments ,
but for now i just put them in one line
i also use some help rules when breaking arguments, liek i connoit break if there is no space
for example

foo 1-2 //wont break
foo 1 -2 //will break

(not all spaces break but if there is a break it is on space or |, without space or | there is no break