Conditional Statemens
This is just some kind of auto wrapping text for testing purposes. The semantic content is totally irrevant. In fact you are currently wasting your time by reading this at all. Nevertheless I am going to continue writing all kind of crap here, just to get some decent amount of characters onto the screen for seeing various aspects of the final layout and its considerations that may be needed to be taken.
This is just some kind of auto wrapping text for testing purposes. The semantic content is totally irrevant. In fact you are currently wasting your time by reading this at all. Nevertheless I am going to continue writing all kind of crap here, just to get some decent amount of characters onto the screen for seeing various aspects of the final layout and its considerations that may be needed to be taken.
A deeper view
This is just some kind of auto wrapping text for testing purposes. The semantic content is totally irrevant. In fact you are currently wasting your time by reading this at all. Nevertheless I am going to continue writing all kind of crap here, just to get some decent amount of characters onto the screen for seeing various aspects of the final layout and its considerations that may be needed to be taken.
Function Name | Description |
---|---|
message() | Print a debug message |
wait() | Suspend execution for certain amount of microseconds. |
message() | Print a debug message |
wait() | This is just a test. Suspend execution for certain amount of microseconds. |
- Point one. Because this is a bla bla bla and so you can do la lal al.
- Point two. And this is another line bla here and there and even thing.
- Point one. Because this is a bla bla bla and so you can do la lal al.
- Point two. And this is another line bla here and there and even thing.
- Point one. Because this is a bla bla bla and so you can do la lal al.
- Point two. And this is another line bla here and there and even thing.
This is just some kind of auto wrapping text for testing purposes. The semantic content is totally irrevant.
In fact you are currently wasting your time by reading this at all. Nevertheless I am going to continue
writing all kind of crap here, just to get some decent amount of characters onto the screen for seeing
various aspects of the final layout and its considerations that may be needed to be taken.
And this is a paragraph with a fairly
large image. It should automatically be constrained by the CSS
rules in case the screen size gets too small.
This is just some kind of auto wrapping text for testing purposes. The semantic content is totally irrevant.
In fact you are currently wasting your time by reading this at all. Nevertheless I am going to continue
writing all kind of crap here, just to get some decent amount of characters onto the screen for seeing
various aspects of the final layout and its considerations that may be needed to be taken.
And this is a sole and centered image:

And this another one:

And even more
This is just some kind of auto wrapping text for testing purposes. The semantic content is totally irrevant. In fact you are currently wasting your time by reading this at all. Nevertheless I am going to continue writing all kind of crap here, just to get some decent amount of characters onto the screen for seeing various aspects of the final layout and its considerations that may be needed to be taken.
The next level
This is just some kind of auto wrapping text for testing purposes. The semantic content is totally irrevant. In fact you are currently wasting your time by reading this at all. Nevertheless I am going to continue writing all kind of crap here, just to get some decent amount of characters onto the screen for seeing various aspects of the final layout and its considerations that may be needed to be taken.
declare const $SIZE := Some Numeric Value
And this could be:
declare const $SIZE := 5
The foo bar is the thing lala la. And you could do i := 4
, because bla bla and
la is 4
.
And more
This is just some kind of auto wrapping text for testing purposes. The semantic content is totally irrevant. In fact you are currently wasting your time by reading this at all. Nevertheless I am going to continue writing all kind of crap here, just to get some decent amount of characters onto the screen for seeing various aspects of the final layout and its considerations that may be needed to be taken.
Break it down
This is just some kind of auto wrapping text for testing purposes. The semantic content is totally irrevant. In fact you are currently wasting your time by reading this at all. Nevertheless I am going to continue writing all kind of crap here, just to get some decent amount of characters onto the screen for seeing various aspects of the final layout and its considerations that may be needed to be taken.
- { Array variables are always global variables, with constant size defined at
- parse time. Trying to declare an array size with a runtime expression (i.e. a
- non const variable), will cause a parser error. }
- SET_CONDITION(DEBUG)
- on init
- declare const $SIZE := 5
- declare %a[$SIZE] := ( 0,1,2,3,4 )
- declare $i
- message("num_elements(%a) = " & num_elements(%a))
- USE_CODE_IF(DEBUG)
- declare const @str := "Initial values of array:"
- message(@str)
- END_USE_CODE
- $i := Value
- $i := 0
- while ($i < $SIZE)
- message("array[" & $i & "] = " & %a[$i])
- $i := $i + 1
- end while
- %a[0] := 2
- %a[1] := 3
- %a[2] := 5
- %a[3] := 7
- %a[4] := 11
- message("")
- message("New values of array:")
- $i := 0
- while ($i < $SIZE)
- message("array[" & $i & "] = " & %a[$i])
- $i := $i + 1
- end while
- end on
Break it down
This is just some kind of auto wrapping text for testing purposes. The semantic content is totally irrevant. In fact you are currently wasting your time by reading this at all. Nevertheless I am going to continue writing all kind of crap here, just to get some decent amount of characters onto the screen for seeing various aspects of the final layout and its considerations that may be needed to be taken.
- { Array variables are always global variables, with constant size defined at
- parse time. Trying to declare an array size with a runtime expression (i.e. a
- non const variable), will cause a parser error. }
- SET_CONDITION(DEBUG)
- on init
- declare const $SIZE := 5
- declare %a[$SIZE] := ( 0,1,2,3,4 )
- declare $i
- message("num_elements(%a) = " & num_elements(%a))
- USE_CODE_IF(DEBUG)
- declare const @str := "Initial values of array:"
- message(@str)
- END_USE_CODE
- $i := 0
- while ($i < $SIZE)
- message("array[" & $i & "] = " & %a[$i])
- $i := $i + 1
- end while
- %a[0] := 2
- %a[1] := 3
- %a[2] := 5
- %a[3] := 7
- %a[4] := 11
- message("")
- message("New values of array:")
- $i := 0
- while ($i < $SIZE)
- message("array[" & $i & "] = " & %a[$i])
- $i := $i + 1
- end while
- end on
This is just some kind of auto wrapping text for testing purposes. The semantic content is totally irrevant. In fact you are currently wasting your time by reading this at all. Nevertheless I am going to continue writing all kind of crap here, just to get some decent amount of characters onto the screen for seeing various aspects of the final layout and its considerations that may be needed to be taken.