typedef char* problem

[Sai-Lai Lo]

Niels Basjes <basjes@nlr.nl> writes:

> So what you are saying is that this is a bug in the Orbix 2.0.1 which they
> solved in a later version.

Yes.

> Why don't you generate a "#define SomeValue char*" instead of the typedef?
> This would make the code more readable and better to maintain. What if
> you decide to change SomeValue into an other type, you would have to
> search all your source code for problem situations.

What if you define SomeValue inside a module X? Your code's reference to
X::SomeValue suddenly becomes X::char*?


-- 
E-mail:         S.Lo@orl.co.uk          |       Olivetti & Oracle Research Lab
                                        |       24a Trumpington Street
Tel:            +44 223 343000          |       Cambridge CB2 1QA
Fax:            +44 223 313542          |       ENGLAND