Ticket #7003 (assigned)

Opened 7 years ago

Last modified 5 years ago

Can we do better than the ugly Property::getUnmangledTypeName function

Reported by: Martyn Gigg Owned by: Martyn Gigg
Priority: major Milestone: Backlog
Component: Framework Keywords: Maintenance
Cc: Blocked By:
Blocking: Tester:

Description

This was a very dirty hack along time ago so that we had a consistent unmangled type string across platforms.

Visual Studio returns unmangled strings by default in type info & GCC offers access to a demangler function: ​http://gcc.gnu.org/onlinedocs/libstdc++/manual/ext_demangling.html

This of course may not then be consistent but it seems good enough for boost::python as that's what they use.

Change History

comment:1 Changed 7 years ago by Nick Draper

  • Owner set to Martyn Gigg
  • Status changed from new to assigned

comment:2 Changed 7 years ago by Martyn Gigg

  • Milestone changed from Release 2.6 to Release 2.7

Batch move to 2.7

comment:3 Changed 7 years ago by Nick Draper

  • Status changed from assigned to new

comment:4 Changed 7 years ago by Nick Draper

  • Milestone changed from Release 2.7 to Backlog

comment:5 Changed 7 years ago by Nick Draper

  • Component changed from Mantid to Framework

comment:6 Changed 7 years ago by Nick Draper

  • Status changed from new to assigned

Bulk move to assigned at the introduction of the triage step

comment:7 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​7849

Note: See TracTickets for help on using tickets.