On Thu, Jan 24, 2013 at 12:57 AM, Peter Soetens <peter [..] ...>wrote:

> Hi Adolfo !
>
> On Wed, Jan 23, 2013 at 5:43 PM, Adolfo Rodríguez Tsouroukdissian
> <adolfo [dot] rodriguez [..] ...> wrote:
> > All,
> >
> > Here's some things that don't work as advertised in the Component
> Builder's
> > manual for 2.6.0:
> >
> > - In 2.2, Starting your first application: C++ style comments are used
> like
> > this: "command // comment". The scripting parser chokes on this, as it
> > allows // at the beginning of a line, but not in the middle. From [2] it
> is
> > not clear whether the bug is in the documentation ( remove inline
> comments)
> > or the parser (support inline comments).
>
> Bug in the parser.
>

So the actual error message is:

"Parse error at line 1: Syntactic error: End of statement expected. Use a
newline or ';' to separate statements."

If either a semicolon or a newline is provided, it works as advertised.
Tested examples:

// This works fine
var double foo // This works fine because the next line is empty

var double bar // This fails because the next line contains a statement
var double baz

var double bar2; // This works fine because of the trailing semicolon
var double baz2

So, documentation bug or scripting enhancement request?.

> >
> > - In 2.5 calling an operation: getPeriod works, but getPeriod.call()
> fails
> > with:
> > Service or Task "Hello" has no Peer or Service getPeriod (or Hello was
> not
> > found at all).
>
> Bug in the parser.
>

http://bugs.orocos.org/show_bug.cgi?id=1021

>
> >
> > - In 2.6 sending an operation: the second example seems to be missing the
> > declaration of ret, something like
> > var double ret
>
> ack.
>

http://bugs.orocos.org/show_bug.cgi?id=1020

Adolfo.

>
> >
> > The latter is clearly a documentation issue, but the first two are not so
> > clear-cut. Please advise so I can appropriately file a bug.
>
> Peter
>