Bug 1937

Summary:	#include <foo.idl> generates invalid code in my opinion :)
Product:	TAO	Reporter:	Markus Stenberg <markus.stenberg>
Component:	IDL Compiler	Assignee:	DOC Center Support List (internal) <tao-support>
Status:	ASSIGNED ---
Severity:	normal
Priority:	P5
Version:	1.4.2
Hardware:	x86
OS:	Linux

Description Markus Stenberg 2004-09-20 02:27:25 CDT

assuming we have statement in bar.idl that says

#include <foo.idl>

what is generated to the barC.cpp for example is

#include "fooC.h"

which in my opinion is not correct behavior.. System<>user distinction should be
maintained.

Comment 1 Jeff Parsons 2004-09-20 09:19:06 CDT

What you're suggesting is unclear. Do you mean that <xxx.idl> should
generate NO C++ include or that it should generate
#include <xxxC.h>?

Comment 2 Markus Stenberg 2004-09-22 01:58:39 CDT

Considering the original reference in the .idl is in <>s, _and_ I use -in flag
for tao_idl, not creating #include <xxxC.h>:s is definitely a bug in my opinion.

Comment 3 Jeff Parsons 2004-09-23 10:41:30 CDT

See my comment in Bug 1927 that references this bug.