typeid + toString = runtime error
    Ali Çehreli 
    acehreli at yahoo.com
       
    Mon Dec 31 09:11:28 PST 2012
    
    
  
On 12/31/2012 03:30 AM, monarch_dodra wrote:
 > //----
 > ~this() {writeln(typeid(this).toString, "is dead");}
 > //----
 >
 > Fixed! ... right?
 >
 > If not, multy write?
That still doesn't help with the case where e.g. a value has a special 
toString() defined and that toString() allocates memory.
Such problems make it impossible to call anything in the destructor 
without knowing their implementations.
I wonder whether the OP's problem actually is a runtime bug? Operations 
like ~ should still be available in the destructors. If not, what is 
available? Do we know the list, inclusive or exclusive?
Ali
    
    
More information about the Digitalmars-d-learn
mailing list