Function Vs Statement?

[AF2013]

Which is better as are both the same?

I did the function and run the program but it is crash the system! So frustrating

[phipslk]

Could you show the code?

Gesendet von meinem Mi Note 10 Lite mit Tapatalk

[E-Penguin]

Originally Posted by AF2013

Which is better as are both the same?

Functions return a value, statements don't.

[AF2013]

Originally Posted by E-Penguin

Functions return a value, statements don't.

Ahhh Right, When I used Statement to show Circle or Square on the screen by using Statement(once I understand on how work then I will be using it more!)

Screen 0,0,0,320,200,3,0,"Welcome Blitz 2",1,2,0

Statement Draw_Everythings{}
                Bitmap 0,320,200,3
                Circlef 160,100,50,3 
                mousewait
End Statement

Draw_Everythings{}
End

I dont understand why doesnt work

[Daedalus]

The Statement/Function thing doesn't look like it's the issue in your code. What error are you getting in the debugger? It looks like you're trying to open a screen with a bitmap that doesn't exist yet. Try moving the Bitmap command out of the statement and before the screen command.

[AF2013]

Originally Posted by Daedalus

The Statement/Function thing doesn't look like it's the issue in your code. What error are you getting in the debugger? It looks like you're trying to open a screen with a bitmap that doesn't exist yet. Try moving the Bitmap command out of the statement and before the screen command.

No Errors and it was showing Welcome Blitz 2 words few seconds then it crash the system as The code I did blow was this

Bitmap 0,320,200,3
Screen 0,0,0,320,200,3,0,"Welcome Blitz 2",1,2,0

Statement Draw_Everythings{}
                
                Circlef 160,100,50,3 
                mousewait

End Statement

Draw_Everythings{}
End

I was hoping that if I can get Statement working then I will be used While and wend loop to create game of moving things hopefully......somethings like this

Open Screen

While Press Escape
      Move_Ball{}
      Move_Bat{}
      Print_Score{}   
wend
End

[Daedalus]

I've just tested this, and the first code does give errors with the debugger running ("Uninitialised Bitmap"). You should always run the debugger while you're testing new code, because it'll catch many issues like that and give you hints about the issue instead of letting the system crash.

Moving the Bitmap command to the top lets it work just fine, and the program structure looks good to me