[Ipopt-tickets] [Ipopt] #145: Entry points for SmartPtrs sometime have SmartPtrs on NEC/SuperUX

[Ipopt]

#145: Entry points for SmartPtrs sometime have SmartPtrs on NEC/SuperUX
------------------------------------------+---------------------------------
  Reporter:  joe.griffin@…                |       Owner:  ipopt-team
      Type:  clarification                |      Status:  new       
  Priority:  normal                       |   Component:  Ipopt     
   Version:  3.9                          |    Severity:  major     
Resolution:                               |    Keywords:  smartptr  
------------------------------------------+---------------------------------

Comment (by joe.griffin@…):

 Andreas,

 The "entry point" is the name in the object that is referenced for the
 subroutine name.  I am old, perhaps "entry point" is a "FORTRANism" name.
 Anyway, one subroutine calls a name with SmartPtr in the name, but the
 routine being called does NOT have SmartPtr and other pieces in the name.

 I know that C++ mangles names somewhat, but I do not know why one name has
 SmartPtr in it, but not the other.

 The SuperUX compiler says it supports SmartPtrs.  I contacted NEC and they
 think that the code has issues.    I was just wondering if there was a
 CONFIG setting for "mangling" the names.

 Thanks,
 Joe

-- 
Ticket URL: <https://projects.coin-or.org/Ipopt/ticket/145#comment:3>
Ipopt <http://projects.coin-or.org/Ipopt>
Interior-point optimizer for nonlinear programs.