Issue 732:  Typo in C++ mapping (cxx_revision)
Source:  (, )
Nature:  Uncategorized Issue
Severity:  Minor
Summary: Summary: C++ mapping in CORBA 2.1 has a typo in the array mapping (section 18.15 page 18-33).Same typo appears in orbos/97-05-15 in section 16.12 page 16-33. It would be nice to actually show the C++ definitions for the types F, V, and M. Find details in corresponding file

Resolution:  Fixed in CORBA 2.2 editing process
Revised Text: 
Actions taken:
September 25, 1997: received issue
February 26, 1998: closed issue
Discussion: 

End of Annotations:=====
Return-Path: <michi@foxtail.dstc.edu.au>
X-Authentication-Warning: foxtail.dstc.edu.au: michi owned process
doing -bs
Date: Thu, 25 Sep 1997 09:38:04 +1000 (EST)
From: Michi Henning <michi@dstc.edu.au>
To: issues@omg.org, cxx_revision@omg.org, port-rtf@omg.org
Subject: Typo in C++ mapping

Hi,

the C++ mapping in the 2.1 spec has a minor editorial glitch in the
array mapping (section 18.15, page 18-33). The same glitch also
appears
in 97-05-15, in section 16.12, page 16-33):

	// IDL
	typedef float F[10];
	typedef string V[10];
	typedef string M[1][2][3];
	void op(out F p1, out V p2, out M p3);

	// C++
	F f1; F_var f2;
	V v1; V_var v2;
	M m1; M_var m2;
	f(f2, v2, m2);
	f1[0] = f2[1];
	// ...

It would be nicer to actually show the C++ definitions for the types
F, V, and M (reading the spec up to this point, it is not yet clear
what
the corresponding generated C++ looks like).

Simply add

	typedef CORBA::Float	F[10];
	typedef char *		V[10];
	typedef char *		M[1][2][3];

to the beginning of the C++ code.

This would make the example a bit clearer and easier to understand.

							Cheers,

								Michi.

--
Michi Henning              +61 7 33654310
DSTC Pty Ltd               +61 7 33654311 (fax)
University of Qld 4072     michi@dstc.edu.au
AUSTRALIA
http://www.dstc.edu.au/BDU/staff/michi-henning.html