search for: getitaniumdemangledbasenam

...r example), and the code for doing that is quite ugly. It would be much nicer if we could just query the parsed representation of the name somehow, and the AST would enable us to do that. I was thinking about this use case a little, actually. I think it makes more sense to provide a function, say getItaniumDemangledBasename(), which could just parse and query the AST for the base name (the AST already has an way of doing this). This would allow the demangler to bail out if it knows that the rest of the input string isn’t relevant, i.e., we could bail out after parsing the ‘foo’ in _Z3fooiiiiiii. That, and not having...

...It would be much nicer if we >> could just query the parsed representation of the name somehow, and >> the AST would enable us to do that. >> >> >> I was thinking about this use case a little, actually. I think it makes more >> sense to provide a function, say getItaniumDemangledBasename(), which could >> just parse and query the AST for the base name (the AST already has an way >> of doing this). This would allow the demangler to bail out if it knows that >> the rest of the input string isn’t relevant, i.e., we could bail out after >> parsing the ‘foo’ in...

On 6/21/17 5:42 PM, Rui Ueyama wrote: > I'm very interested in your work because I've just started writing a > demangler for the Microsoft mangling scheme. What I found in the > current Itanium demangler is the same as you -- it looks like it > allocates too much memory during parsing and concatenates std::strings > too often. I could see there's a (probably big)