www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.bugs - [Issue 994] New: incorrect name mangling of RT symbols for "special" classes

reply d-bugmail puremagic.com writes:
http://d.puremagic.com/issues/show_bug.cgi?id=994

           Summary: incorrect name mangling of RT symbols for "special"
                    classes
           Product: D
           Version: 1.005
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P3
         Component: DMD
        AssignedTo: bugzilla digitalmars.com
        ReportedBy: thomas-dloop kuehne.cn


The most obvious example is object.Object:

_D6Object6__initZ
_D6Object6__vtblZ
_D6Object7__ClassZ
_D6object6Object5opCmpMFC6ObjectZi
_D6object6Object8opEqualsMFC6ObjectZi
_D6object6Object6toHashMFZk
[...]

affected classes:
ModuleInfo (std.moduleinit.ModuleInfo)
Object (object.Object)
Exception (object.Exception)
ClassInfo (object.ClassInfo)
TypeInfo (object.TypeInfo)


--
Feb 21 2007
next sibling parent d-bugmail puremagic.com writes:
http://d.puremagic.com/issues/show_bug.cgi?id=994


bugzilla digitalmars.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID





This is by design.


--
Mar 09 2007
prev sibling next sibling parent d-bugmail puremagic.com writes:
http://d.puremagic.com/issues/show_bug.cgi?id=994








 This is by design.


Why _D6Object7__ClassZ instead of _D6object6Object7__ClassZ?


--
Mar 09 2007
prev sibling parent d-bugmail puremagic.com writes:
http://d.puremagic.com/issues/show_bug.cgi?id=994






They are special classes - it may be worthwhile to split or move them into
different modules, and I don't want to break binary compatibility doing so.


--
Mar 09 2007