OpenEuphoria

section 4.2.1 it is said that Identifiers must start with a letter
with version 4 underscores are accepted too, should be corrected.

section 4.2.1.1

procedure bar(sequence s="abc", integer n, integer p=1)  
    ? length(s)+n+p  
end procedure  

s paramater should be after n as n is mandaroty

section 4.2.3.3

-- lib.e  
namespace lib.e  

this should be namespace lib

There is a contradiction between 4.4.3 first sentence The ifdef statement is unlike all of the other statements in that it is executed at parse time not runtime.
and section 4.4.3.3
Is ifdef parse time or run time?

Thanks ... this has now been fixed in the docs.

procedure bar(sequence s="abc", integer n, integer p=1)  
    ? length(s)+n+p  
end procedure  

No it doesn't have to be. There is no requirement in Euphoria for mandatory parameters to come before optional parameters. You can mix them in any way that is appropriate for your routine's usage. The above example is saying that as the second parmeter is mandatory, you must always supply a second parameter. The first and third are optional and can be omitted from the calling code. To omit the first parameter you would code ...

  bar(, 4) 

-- lib.e  
namespace lib.e  

Thanks, this is now fixed in the docs.

I don't see what the contradiction is. Can you show me both sentences to show me what is being contradicted.

The ifdef is executed during the parsing phase. That means that there is NO intermediate language code (IL) generated for the ifdef itself. Remember that the runtime phase only executes IL code.

To recap, the interpreter has two phases - parse-time and run-time. During the parse time, the source code is examined for validity and is converted to IL code. During run time, the IL code is executed, thus bringing your application to life. The ifdef statements are executed by the parser to select optional parts of your source code to convert to IL code.

for X = 1 to 10 do 
ifdef DEBUG then 
    display("DEBUG: Value of X is []", X) 
end ifdef 
    foo(X) 
end for 

The generated IL code for this source depends on if DEBUG has been defined or not. If it is not defined the generated IL code will be for ...

for X = 1 to 10 do 
    foo(X) 
end for 

But if it was defined, the generated IL code would be for ...

for X = 1 to 10 do 
    display("DEBUG: Value of X is []", X) 
    foo(X) 
end for