[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference pamsrc::objectbroker_development

Title:	ObjectBroker Development - BEA Systems' CORBA
Notice:	See note 2 for kit locations; note 4 for training
Moderator:	RECV::GUMBELd

Created:	Thu Dec 27 1990
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	2482
Total number of notes:	13057

2423.0. "Use of French characters in IDL file comments" by PEACHS::SELBY (I am Pentium of Borg. Prepare to be approximated.) Fri Jan 24 1997 11:59

One of my Canadian customers is trying to add comments to his IDL 
code.  He would like to use French in the comments, however, the
characters are causing ObjectBroker problems.  Is there anyway to
include French characters in comments?

Below is a very simple IDL file that will duplicate the customer's
problem.  If you try to generate the UUIDs for this IDL, it will
generate the error:

	$ appl/broker gen unique/idl=unicode.idl

e pour M�
       ^
%OBB-F-CMD_SYNTAXERROR, Fatal syntax error.
                At line number 21 in DSA1:[SELBY]UNICODE.IDL;2.

%OBB-F-FATAL, Fatal error detected.


Is there anyway to get this to work, or is this a limitation of
the product?

Thanks

Dale Selby
CSC Alpharetta


//==============================================================================
//===  IDL NUMBER 1.  ===
//==============================================================================
//
//  Used in BANK EXAMPLE 1.
//
//  Description:
//
//     This rudimentary IDL example illustrates the basics of defining
//     modules, interfaces and operations.  Because of its simplicity,
//     it represents a totally unrealistic model for a banking application,
//     but it is a good learning tool and can easily be built upon to
//     highlight other features of ObjectBroker.
//
//
//==============================================================================


/* Comments by Thi�n B�i */
// cette fonction est utilis�e pour M�J seulement le Groupe Action concern�

//  While CORBA does not require the use of modules, it is good programming
//  practice to group related interface definitions together within a module.
//  For our examples, we shall define all our interfaces within the module
//  BANK.

module BANK                                    // module declaration

{

   interface CheckAcct {                       // interface declaration

      float get_balance ( );                   // operation declaration

   };

};  // end of module BANK

T.R	Title	User	Personal Name	Date	Lines
2423.1		SEND::SLAVIN		`Fri Jan 24 1997 12:53`	1
	ISO LATIN 1 is the only supported character set.
2423.2		PEACHS::SELBY	I am Pentium of Borg. Prepare to be approximated.	`Fri Jan 24 1997 13:13`	13
	> >ISO LATIN 1 is the only supported character set. > Just wanted to check. I willdo a request for functionality. Basically, the customer would like to place comments in their language instead of English. This isn't too much trouble in Canada, but I can see the need in other locales. Thanks! Dale
2423.3		SEND::SLAVIN		`Fri Jan 24 1997 13:51`	4
	I'm not sure but I don't think the tools we use in the compiler support other character sets. We use yacc, so we would need a yacc that supports other sets on all our platforms and a business need to make the change.
2423.4	I believe Latin-1 is enough to enter in French	CFSCTC::HUSTON	Steve Huston	`Fri Jan 24 1997 15:48`	7
	If they can type non-Western Latin-1 characters into the file, that should be good for entering French (though I'm _way_ out of my specialty here...) If the compiler is choking on characters with the eighth bit set, that's a legitimate bug. Latin-1 is a full 8 bit set. -Steve
2423.5		OSAV03::NOSE	Tooru Nosse, Japan West PSC/OS2	`Sun Jan 26 1997 08:55`	2
	You could preprocess IDL with cpp if you need solution right now.
2423.6		REQUE::BOWER	Peter Bower, ObjectBroker	`Tue Jan 28 1997 06:49`	4
	I tried the appl/broker gen uniq on the idl in .0 and it worked fine on v2.7-11. What version is the customer using ?
2423.7	2.6 and 2.7-10	PEACHS::SELBY	I am Pentium of Borg. Prepare to be approximated.	`Tue Jan 28 1997 09:16`	6
	I have tried this on 2.6 and on 2.7-10. I will upgrade my NT system to 2.7-11 and see if the problem changes. Thanks. dale
2423.8	...	PEACHS::SELBY	I am Pentium of Borg. Prepare to be approximated.	`Tue Jan 28 1997 10:10`	22
	Still no go. Windows NT 3.51 (Build 1057: Service Pack 4) ObjectBroker 2.7-11 > obgen -f file.idl -u e pour M%J seulement le Groupe Action Concern8 ^ OBB_CMD_SYNTAXERROR (f), Fatal syntax error. At line number 21 in file.idl. > obbsho OBB V2.7-11 Copyright Digital Equipment Corporation 1991, 1996. All rights reserved. I will also try this out on DUnix. What platform did you try it on? dale
2423.9		REQUE::BOWER	Peter Bower, ObjectBroker	`Tue Jan 28 1997 21:54`	7
	> I will also try this out on DUnix. What platform did you try it on? I tried it on VMS as I was dialed in. When I tried it at work on my nt box, I got the same error. I suspect a yacc difference. I will investigate it further in the next few days.
2423.10		EMNTAL::STADELMANN	Sepp @ZUO 760-2609	`Wed Jan 29 1997 05:58`	10
	If you say ISO Latin is supported then you probabbly mean that 7 and 8 bit characters are supported as part of content of a string to be furter processed and after all used in code somehow. But the claim is for French Characters in Comment; Does the compiler not ignore any charcter clearly marked as belonging to comment ? If so then this is the real issue in my mind. Sepp,
2423.11	PTR 16-3-224	REQUE::BOWER	Peter Bower, ObjectBroker	`Fri Jan 31 1997 15:58`	8
	The problem is with the OBB preprocessor. When it encounters the French character, it incorrectly preprocesses the output. Note that this is only a problem with the // comment style. Therefore, the workaround is to use the C style comments /* */ instead of the C++ style comments //