Changes between Initial Version and Version 1 of Ticket #35770, comment 29


Ignore:
Timestamp:
Sep 19, 2012, 6:59:18 AM (7 years ago)
Author:
ryandesign (Ryan Schmidt)
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #35770, comment 29

    initial v1  
    11I also vote to return to the previous state, at least until there is a separate libstc++ port.
    22
    3 I agree that the instability from comment #2 is not theoretical and I can easily reproduce it.  At the same time, I can easily solve the problem by stopping mixing the compilers when I compile my code.   Long time ago there was already a ticket for "pointer being freed was not allocated" error, where the a suggested solution.  While the solution is not really working, the key point is not mixing stuff. 
     3I agree that the instability from comment:2 is not theoretical and I can easily reproduce it.  At the same time, I can easily solve the problem by stopping mixing the compilers when I compile my code.   Long time ago there was already a ticket for "pointer being freed was not allocated" error, where the a suggested solution.  While the solution is not really working, the key point is not mixing stuff. 
    44
    5 Those who is not using gc4[4-8] have no problem.  Those who are using, just need to accept the fact that there is an incompatibility if compilers are mixed.   The removal of std++ solve solvable problem for a subset of developers using gcc, but creates unsolvable problem for others who rely on c++11 and other new features of standard library.
     5Those who is not using gc4![4-8] have no problem.  Those who are using, just need to accept the fact that there is an incompatibility if compilers are mixed.   The removal of std++ solve solvable problem for a subset of developers using gcc, but creates unsolvable problem for others who rely on c++11 and other new features of standard library.