Application is the chief source of conflicting identifiers, and I seldom
refer to it in my Delphi code.  It's easy enough to change those few
references to Forms.Application, which is unique and eliminates the
problem.

Hi all,

In the code, resulting after a typelibrary import are almost always
comments inserted, stating that declaration so and so, or property this
or that has been renamed due to conflicts with reserved words. But I
also see a lot of other declarations using names that also exist in
Delphi, like Application.

An earlier posting suggested to change the name of these type
declarations to avoid conflict with the application object in Delphi.
But can you safely change names of declarations?

I've tried to get a mental picture on the how things fit together by
going over the various declarations and noticed that it was very
difficult to keep track of which is which, there seem to be number of
occurances where the property or class has the exact same name as the
type from which it is derived.

Since I've seen in the inserted comments that Delphi renames
declarations by adding or prefixing an underscore I am wondering if I
can do this myself too. Changing names in declalations, to better
reflect what the identifier's type is I mean.

To what extent can I do this safely,  like, I've seen a lot of interface
declarations start with an i, but in the ...TLB.pas, this is not
consequently done, so sometimes the interface declaration looks like a
regular variable definition or a dispinterface is not prefixed with a d,
thus contributing to my confusion when trying to understand how things
fit together.
So, I'd like to go over the code and change each name that is exactly
the same as the name of the type from which it's derived to something to
distinguish the both of'm.

TIA
Raj Gabrielse
=(email address is bogus, reply_to contains 'almost' correct address)=

Hello Scott,

Thanks for clarifying though, much apppreciated

Raj Gabrielse