This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
vB() versus vB(void)
- From: mec dot gnu at mindspring dot com (Michael Elizabeth Chastain)
- To: drow at mvista dot com
- Cc: carlton at kealia dot com, gdb at sources dot redhat dot com
- Date: Tue, 3 Feb 2004 22:50:53 -0500 (EST)
- Subject: vB() versus vB(void)
I've got this little ptype discrepancy.
gdb HEAD prints:
ptype vB
type = class vB : public virtual vA {
public:
int vb;
int vx;
vB & operator=(vB const&);
vB(vB const&);
vB();
}
gdb drow-cplus-branch prints:
ptype vB
type = class vB : public virtual vA {
public:
int vb;
int vx;
vB & operator=(vB const &);
vB(vB const &);
vB(void);
}
The difference is "vB()" versus "vB(void)".
This is a synthetic ctor. This happens with gcc 3.3.2 and gcc HEAD.
Should I report this as a bug in gdb drow-cplus-branch,
or should I just accept both forms as PASS?
My preference is to accept both forms as PASS, but I want to check
before I do that, in case you think that "vB(void)" is a symptom of a bug.
Michael C