Closed
Bug 489833
Opened 17 years ago
Closed 17 years ago
Dehydra has trouble with type names on templates containing templates
Categories
(Developer Infrastructure :: Source Code Analysis, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: humph, Assigned: dmandelin)
References
Details
Attachments
(1 file)
|
1.31 KB,
application/octet-stream
|
Details |
In trying to parse the body's of funcs for dxr, I'm hitting a problem with the type.name being garbled for templates that contain templates. For example, given:
template<class T> class nsCOMPtr{
public:
nsCOMPtr();
};
class nsIDog;
class nsIDog{};
int f();
int f()
{
nsCOMPtr< nsCOMPtr<nsIDog> > doggy;
}
Here is what I see for the variable doggy
statements: [{
name: "doggy",
type: #1 = {
kind: "class",
name: "nsCOMPtr >",
You can try testing here to see what I mean: http://germany.proximity.on.ca/dehydra-web/process.cgi
| Assignee | ||
Updated•17 years ago
|
Assignee: nobody → dmandelin
| Assignee | ||
Comment 1•17 years ago
|
||
I couldn't duplicate this. The attachment contains my Dehydra script, the test C++ file, the command line I used, and the output. I ran on Linux. I also tried putting that output through the beautifier and it came out OK.
I checked out the output on the test site you linked and I do see the bug there. Looking at the error, it almost makes me wonder if there is some intermediate script that doesn't do so well with spaces. The other obvious thing would be if you're not on the latest Dehydra.
If none of those works, or if I just made some boneheaded mistake, can you give me exactly what scripts and commands you are running so I can try again to dup it?
| Reporter | ||
Comment 2•17 years ago
|
||
You're right, this is < vs. < in my python script. Sorry to waste your time!
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
Updated•8 years ago
|
Product: Core → Firefox Build System
Updated•3 years ago
|
Product: Firefox Build System → Developer Infrastructure
You need to log in
before you can comment on or make changes to this bug.
Description
•