Bug 1937 - #include <foo.idl> generates invalid code in my opinion :)
Summary: #include <foo.idl> generates invalid code in my opinion :)
Status: ASSIGNED
Alias: None
Product: TAO
Classification: Unclassified
Component: IDL Compiler (show other bugs)
Version: 1.4.2
Hardware: x86 Linux
: P5 normal
Assignee: DOC Center Support List (internal)
URL:
Depends on:
Blocks:
 
Reported: 2004-09-20 02:27 CDT by Markus Stenberg
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 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.