Closed GoogleCodeExporter closed 9 years ago
Thanks for reporting, we will analyse this.
Original comment by klaus.birken@gmail.com
on 17 May 2013 at 8:28
The problem is that the undefined annotation is parsed as the text of the
previous annotation. This cannot really be avoided, only if the undefined tag
also has some special distinguishing character at the beginning.
Original comment by szabt...@gmail.com
on 21 May 2013 at 11:00
This issue can be resolved either by:
- adding the usual @-tag at the beginning of the keyword "undefined"
- removing the undefined-tag completely.
The undefined-tag has been introduced only for being able to transform
meta-data from other IDLs without using one of the existing tags. This is a bad
idea anyway => we will remove the undefined-tag in the comments in the next
release (v.0.8.8).
Original comment by klaus.birken@gmail.com
on 10 Jun 2013 at 2:25
Original comment by klaus.birken@gmail.com
on 10 Jun 2013 at 2:39
Original comment by klaus.birken@gmail.com
on 11 Jul 2013 at 11:25
Original issue reported on code.google.com by
mszcz...@gmail.com
on 17 May 2013 at 5:40