← Back to index | Original Bugzilla link

Bug 2649 – Inconsistent naming in TypeInfo derived classes

Status: RESOLVED
Resolution: WORKSFORME
Severity: normal
Priority: P4
Component: dmd
Product: D
Version: D1 (retired)
Platform: x86
OS: Linux
Creation time: 2009-02-07T11:04:01Z
Last change time: 2019-09-10T09:46:25Z
Assigned to: No Owner
Creator: Neia Neutuladh

Comments

Comment #0 by dhasenan — 2009-02-07T11:04:01Z

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.

Comment #1 by razvan.nitu1305 — 2019-09-10T09:46:25Z

There is a new hierarchy now. TypeInfoDeclarations are all VarDeclarations so they have the same names for most of the fields. All TypeInfoDeclarations inherit TypeInfoDeclaration so all inconsistencies are gone. Closing as WORKSFORME.