Issue 264:  make String_var reference but not adopt (cxx_revision)
Source:  (, )
Nature:  Uncategorized
Severity:  ENHANCEMENT
Summary: Summary: String_var could refer to memory without assuming memory management responsibilities for it, like void String_var::value(const char*, Boolean release = 0

Resolution: close with no change
Revised Text: 
Actions taken:
October 14, 1996: received issue
June 13, 2000: closed issdue
Discussion: 
Close with no change. The _var type usage is so entrenched now that to change the memory-management behavior would
break just about every C++ CORBA program in existence.
End of Annotations:=====
This is issue # 264


make String_var reference but not adopt 

String_var could refer to memory without assuming memory          
          management responsibilities for it, like void                     
          String_var::value(const char*, Boolean release = 0 


-Juergen