http://d.puremagic.com/issues/show_bug.cgi?id=2649
Summary: Inconsistent naming in TypeInfo derived classes Product: D Version: 1.036 Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P4 Component: DMD AssignedTo: bugzi...@digitalmars.com ReportedBy: dhase...@gmail.com Most members of TypeInfo and derived classes are named simply, eg "next", "value", "name". There are exceptions: - TypeInfo_Typedef.m_init - TypeInfo_Pointer.m_next - TypeInfo_Struct.m_init - TypeInfo_Struct.m_flags Also, TypeInfo_Pointer has its value type as "m_next", whereas TypeInfo_Array has its value type as "value". These are needless inconsistencies. I'd like to see them done away with. --