This is a snipped from a doxygen comment explaining the use of comments in SQL:
- ##NAME[::TYPE[::NULL]]: for a variable named NAME with the optional type
TYPE
* (which can be a GType name or a custom database type name), and with the
* optional "::NULL" to instruct that the variable can be NULL.
* - ## \/* name:NAME [type:TYPE] [nullok:[TRUE|FALSE]] [descr:DESCR] *\/
* for a variable named NAME with the optional type TYPE (which can be a GType
* name or a custom database type name), with the optional "nullok" attribute
* and an optional description DESCR. Note that the NAME, TYPE and DESCR
literals here
* must be quoted (simple or double quotes) if they include non alphanumeric
* characters, and that there must always be at least a space between the
* ## and the \/* ... *\/.
As you see it contains "/* */" but those are correctly escaped. Nevertheless,
gcc/g++ reports a warning "/* within comment" twice. IMHO this is the wrong
behaviour as the comment is valid and contains correctly escaped code.
--
Summary: Warning about correctly escaped comment
Product: gcc
Version: 4.3.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: jhs at gnome dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38103
