Bug 1390 - Valuetypes have call-by-reference semantics in collocated calls
Summary: Valuetypes have call-by-reference semantics in collocated calls
Status: ASSIGNED
Alias: None
Product: TAO
Classification: Unclassified
Component: IDL Compiler (show other bugs)
Version: 1.2.3
Hardware: All All
: P3 major
Assignee: DOC Center Support List (internal)
URL:
Depends on: 1369 1391
Blocks: 2454
  Show dependency tree
 
Reported: 2002-12-06 20:40 CST by Nanbor Wang
Modified: 2018-01-15 11:21 CST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nanbor Wang 2002-12-06 20:40:27 CST 
Valuetypes should always be passed by value.  However, TAO's collocated 
invocations pass valuetypes as references.  I.e., servants can change the 
passed in parameters in collocated invocations, which is wrong.  

Need to change the IDL compiler to create a copy for both ThruPOA and Direct 
proxies.
Comment 1 Nanbor Wang 2002-12-07 08:24:15 CST 
Looks like this bug depends on 1391.
Comment 2 Jeff Parsons 2002-12-15 12:51:42 CST 
Accepted. Maybe Boris can work on this.
Comment 3 Johnny Willemsen 2004-05-11 05:09:28 CDT 
The test TAO\tests\OBV\Collocated\Forward is failing because of this problem. I 
see this for example on Solaris, MSVC6 and Borland. On some builds this tests 
runs without problems, strange however.
Comment 4 Carlos O'Ryan 2004-11-19 15:53:54 CST 
I believe it will be easier to fix this problem once bug 1369 is fixed.
Comment 5 Johnny Willemsen 2005-03-15 03:23:03 CST 
I wonder if this is now easier to fix with all refactoring that is currently 
done. This test is still failing.
Comment 6 Jeff Parsons 2006-02-10 09:47:35 CST 
See today's comment in 1391
Comment 7 Johnny Willemsen 2006-03-21 05:11:22 CST 
will be handled by Remedy
Comment 8 Johnny Willemsen 2006-03-21 05:11:30 CST 
accept
Comment 9 Johnny Willemsen 2006-12-05 09:49:38 CST 
to pool again
Comment 10 Jeff Parsons 2006-12-06 11:05:47 CST 
We are talking only about IN arguments, right? In all other cases, don't we 
want the arguments to change when the servant modifies them?