By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
445,717 Members | 2,069 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 445,717 IT Pros & Developers. It's quick & easy.

Having my own "System" class causes compiler error

P: n/a

We have an internal tool that generates a series of .NET class wrappers
for accessing our database entities. One of our database entities is
called "System" so our correspond __gc class is called System. All of
our classes are declared in our own namespace X.

We are getting an error message along the lines of:

Error C2027: use of undefined type 'X::System'. SuppressFinalize
identifier not found. This diagnostic occurred in the compiler
generated function X::Entity::~Entity.

So it would seem that this compiler generated code for the destructor
is somehow getting confused between our System class and the System

Now, for the purposes of investigation, we change 'System' to 'SystemX'
everything is fine. But since our code is auto-generated code, that is
not really a practical solution.

We thought that by having our classes in our X namespace we would be
reasonably well isolated from these problems.

We have tried coding our own destructor on these classes also and it
seems to make no difference.

Any help on getting around this would be appreciated.

Nov 17 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.