Your message dated Sun, 13 May 2012 23:02:27 +0300
with message-id <[email protected]>
and subject line Re: Bug#435009: doxygen: Incorrect "[read]" in C struct-type 
member
has caused the Debian Bug report #435009,
regarding doxygen: Incorrect "[read]" in C struct-type member
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
435009: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=435009
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: doxygen
Version: 1.5.3-1
Severity: minor

In doxygen-1.5.2/src/memberdef.cpp, MemberDef::writeDocumentation
writes "read" if isReadable() returns true, which it does if the
Entry::Readable flag is set.  This flag is set by the
<QtPropAttr>"READ" rule in doxygen-1.5.3/src/scanner.l, so it
apparently is related to the Qt "Q_PROPERTY" construct.  The
following demonstration does not use any Qt-specific syntax but
Doxygen regardless displays "[read]" in the documentation of the
outer::bug member.  The cause seems to be that Doxygen defines
both Entry::Readable and Entry::Struct as 0x0020 and doesn't
remember which one it meant.

/*! \file
 * \brief Demonstration of incorrect [read] emitted by Doxygen 1.5.2
 * and 1.5.3 */

/*! \brief Inner structure */
struct inner {
  /*! \brief Some member */
  int x;
};

/*! \brief Outer structure */
struct outer {
  /*! \brief Doxygen 1.5.2 and 1.5.3 incorrectly tag this as [read].  */
  struct inner bug;
};

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.21-1-k7
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)

Versions of packages doxygen depends on:
ii  libc6                         2.3.6-7    GNU C Library: Shared libraries
ii  libgcc1                       1:4.1.2-4  GCC support library
ii  libpng12-0                    1.2.8rel-1 PNG library - runtime
ii  libstdc++6                    4.1.2-4    The GNU Standard C++ Library v3

doxygen recommends no packages.

-- no debconf information

Attachment: pgpxxg9o1gqPa.pgp
Description: PGP signature


--- End Message ---
--- Begin Message ---
Version: 1.6.2-1

http://www.stack.nl/~dimitri/doxygen/changelog.html#1.6.2 says
this was fixed as id 598497.  I tested that 1.6.2-1, 1.7.1-1,
1.7.3-6, and 1.7.6.1-2.1 don't have the bug, and that it's still
reproduceable in 1.6.1-1 as previously reported.  The upstream
report https://bugzilla.gnome.org/show_bug.cgi?id=598497 has no
details about the fix.

Attachment: pgpJusSNtiDag.pgp
Description: PGP signature


--- End Message ---

Reply via email to