After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 320975 - multiple line separator ( \ ) is not recognized
multiple line separator ( \ ) is not recognized
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.4.x
Other All
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2005-11-08 15:05 UTC by Angelo Calafato
Modified: 2006-01-03 13:01 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Angelo Calafato 2005-11-08 15:05:48 UTC 
I use C++ language. I use often the multi line separator to split into
different line i.e. class declarations as the following:

class MyClass {
public:
    MyClass(const int  & i = 0,
            const char * myLongStringParameter = \
                MyClass::DEFAULT_STRING_PARAMETER);
};

MyClass::MyClass (const int& i = 0,
                  const char *myLongStringParameter =
\MyClass::DEFAULT_STRING_PARAMETER);
};

So, the character \ is not recognized by Doxygen.
Comment 1 Dimitri van Heesch 2005-11-13 15:39:31 UTC 
Correct. The preprocessor should have stripped them. I'll fix this in the next
CVS update. 

But I do really wonder why you use line separators at places where it is not at
all needed?
Comment 2 Thomas Dickey 2005-12-12 20:40:15 UTC 
Backslashes aren't working as continuation lines for #define's
either.  doxygen gets about halfway through vile's estruct.h
before becoming totally confused.  Here's the macro where it
gets lost:

#define NEXT_COLUMN(col, c, list, tabs) \
                (((c) == '\t' && !(list)) \
                 ? ((col) + (tabs) - ((col) % tabs)) \
                 : (    (isPrint(c)) \
                        ? ((col) + 1) \
                        : ((col) + (((c) & HIGHBIT) ? 4 : 2))))

What sort of regression testing are you doing?
Comment 3 Dimitri van Heesch 2005-12-30 17:48:02 UTC 
This bug had the status ASSIGNED (which meant it was fixed, but not officially released), so now doxygen release 1.4.6 is out I've given it the status FIXED. 

Nevertheless, I would like to ask you to verify that this bug is indeed fixed in release 1.4.6. If not, then please reopen the bug.
Comment 4 Thomas Dickey 2006-01-03 13:01:31 UTC 
I retested and found that neither of the cases I listed here
and in 134216 have changed.